Beam failure recovery with multiple cells

ABSTRACT

A wireless device receives configuration parameters indicating one or more first RSs, on a first cell, as candidate RSs for a BFR procedure of a second cell. The wireless device triggers, in response to a number of beam failure instances on the second cell, the BFR procedure for the second cell. The first cell is deactivated. Based on the deactivating the first cell, the BFR procedure for the second cell is cancelled.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/887,287, filed Aug. 15, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17A and FIG. 17B are example diagrams of a downlink beam failure asper an aspect of an embodiment of the present disclosure.

FIG. 18 is an example flow chart of a downlink beam failure as per anaspect of an embodiment of the present disclosure.

FIG. 19 is an example diagram of a downlink beam failure instanceindication as per an aspect of an embodiment of the present disclosure.

FIG. 20 is an example diagram of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 21 is an example diagram of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 23 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 26 is an example diagram of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 27 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 28 is an example flow chart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 29 is a diagram of flowchart as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNB s 162 may include three sets ofantennas to respectively control three cells (or sectors). Together, thecells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage tothe UEs 156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling.The UE 210 may receive services through a PDU session, which may be alogical connection between the UE 210 and a DN. The PDU session may haveone or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IPpackets to the one or more QoS flows of the PDU session based on QoSrequirements (e.g., in terms of delay, data rate, and/or error rate).The SDAPs 215 and 225 may perform mapping/de-mapping between the one ormore QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3, PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3, the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3), add corresponding headers,and forward their respective outputs to the next lower layer. Forexample, the PDCP 224 may perform IP-header compression and cipheringand forward its output to the RLC 223. The RLC 223 may optionallyperform segmentation (e.g., as shown for IP packet m in FIG. 4A) andforward its output to the MAC 222. The MAC 222 may multiplex a number ofRLC PDUs and may attach a MAC subheader to an RLC PDU to form atransport block. In NR, the MAC subheaders may be distributed across theMAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may beentirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell;    -   a common control channel (CCCH) for carrying control messages        together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6, a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8. An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8. An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9, the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switchingpoint 908. The switching at the switching point 908 may occur for anysuitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB 1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_idwhere s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15, but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15.

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer mayperform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15, a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15, the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

In a carrier aggregation (CA), two or more component carriers (CCs) maybe aggregated. A wireless device may simultaneously receive or transmiton one or more CCs depending on capabilities of the wireless device. Inan example, the CA may be supported for contiguous CCs. In an example,the CA may be supported for non-contiguous CCs.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell for an efficientbattery consumption. When a wireless device is configured with one ormore SCells, a gNB may activate or deactivate at least one of the one ormore SCells. Upon configuration of an SCell, the SCell may bedeactivated.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a base station may transmit, to a wireless device, one ormore messages comprising an sCellDeactivationTimer timer. In an example,a wireless device may deactivate an SCell in response to an expiry ofthe sCellDeactivationTimer timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell, CQI/PMI/RI/CRIreporting for the SCell on a PCell, PDCCH monitoring on the SCell, PDCCHmonitoring for the SCell on the PCell, and/or PUCCH transmissions on theSCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart an sCellDeactivationTimer timer associatedwith the SCell. The wireless device may start the sCellDeactivationTimertimer in the slot when the SCell Activation/Deactivation MAC CE has beenreceived. In an example, in response to the activating the SCell, thewireless device may (re-)initialize one or more suspended configureduplink grants of a configured grant Type 1 associated with the SCellaccording to a stored configuration. In an example, in response to theactivating the SCell, the wireless device may trigger PHR.

In an example, when a wireless device receives an SCellActivation/Deactivation MAC CE deactivating an activated SCell, thewireless device may deactivate the activated SCell.

In an example, when an sCellDeactivationTimer timer associated with anactivated SCell expires, the wireless device may deactivate theactivated SCell. In response to the deactivating the activated SCell,the wireless device may stop the sCellDeactivationTimer timer associatedwith the activated SCell. In response to the deactivating the activatedSCell, the wireless device may stop the BWP inactivity timer associatedwith the activated SCell. In response to the deactivating the activatedSCell, the wireless device may deactivate any active BWP associated withthe activated SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart an sCellDeactivationTimer timer associated with theactivated SCell. In an example, when at least one second PDCCH on aserving cell (e.g. a PCell or an SCell configured with PUCCH, i.e. PUCCHSCell) scheduling the activated SCell indicates an uplink grant or adownlink assignment for the activated SCell, a wireless device mayrestart an sCellDeactivationTimer timer associated with the activatedSCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

In an example of an SCell Activation/Deactivation MAC CE of one octet, afirst MAC PDU subheader with a first LCID may identify the SCellActivation/Deactivation MAC CE of one octet. The SCellActivation/Deactivation MAC CE of one octet may have a fixed size. In anexample of the first LCID, the SCell Activation/Deactivation MAC CE ofone octet may comprise a single octet. The single octet may comprise afirst number of C-fields (e.g. seven) and a second number of R-fields(e.g. one).

In an example of an SCell Activation/Deactivation MAC CE of four octets,a second MAC PDU subheader with a second LCID may identify the SCellActivation/Deactivation MAC CE of four octets. In an example of thesecond LCID, the SCell Activation/Deactivation MAC CE of four octets mayhave a fixed size. The SCell Activation/Deactivation MAC CE of fouroctets may comprise four octets. The four octets may comprise a thirdnumber of C-fields (e.g. 31) and a fourth number of R-fields (e.g. 1).

In an example, a C_(i) field may indicate an activation/deactivationstatus of an SCell with an SCell index i, if a SCell with SCell index iis configured. In an example, when the C_(i) field is set to one, anSCell with an SCell index i may be activated. In an example, when theC_(i) field is set to zero, an SCell with an SCell index i may bedeactivated. In an example, if there is no SCell configured with SCellindex i, the wireless device may ignore the C_(i) field. In an example,an R field may indicate a reserved bit. The R field may be set to zero.

In an example, a wireless device may trigger a SR for requesting UL-SCHresource when the wireless device has new transmission. A gNB maytransmit to a wireless device at least one message comprising parametersindicating zero, one or more SR configurations. A SR configuration maycomprise a set of PUCCH resources for SR on one or more BWPs, and/or oneor more cells. On a BWP, at most one PUCCH resource for SR may beconfigured. Each SR configuration may correspond to one or more logicalchannels. Each logical channel may be mapped to zero or one SRconfiguration configured by the at least one message. A SR configurationof a logical channel (LCH) that triggers a buffer status report (BSR)may be considered as a corresponding SR configuration for a triggeredSR.

In an example, for each SR configuration, the at least one message mayfurther comprise one or more parameters indicating at least one of: a SRprohibit timer; a maximum number of SR transmission; a parameterindicating a periodicity and offset of SR transmission; and/or a PUCCHresource. In an example, the SR prohibit timer may be a duration duringwhich the wireless device may be not allowed to transmit the SR. In anexample, the maximum number of SR transmission may be a transmissionnumber for which the wireless device may be allowed to transmit the SRat most.

In an example, a PUCCH resource may be identified by at least: frequencylocation (e.g., starting PRB); a PUCCH format associated with initialcyclic shift of a base sequence and time domain location (e.g., startingsymbol index).

In an example, a wireless device may maintain a SR transmission counter(e.g., SR_COUNTER) associated with a SR configuration.

In an example, if an SR of a SR configuration is triggered, and thereare no other SRs pending corresponding to the same SR configuration, awireless device may set the SR_COUNTER of the SR configuration to afirst value (e.g., 0).

In an example, when an SR is triggered, a wireless device may considerthe SR pending until it is cancelled. In an example, when one or more ULgrants accommodate all pending data available for transmission, allpending SR(s) may be cancelled.

In an example, a wireless device may determine one or more PUCCHresources on an active BWP as valid PUCCH resources at a time of SRtransmission occasion.

In an example, a wireless device may transmit a PUCCH in a PUCCHresource associated with a SR configuration when the wireless devicetransmits a positive SR. In an example, a wireless device may transmitthe PUCCH using PUCCH format 0, or PUCCH format 1, according to thePUCCH configuration.

In an example, a wireless device may receive one or more RRC messagecomprising parameters of one or more SR configurations. In an example,for each of the one or more SR configurations, the parameters mayindicate at least one of: a SR prohibit timer; a maximum number of SRtransmission; a parameter indicating a periodicity and offset of SRtransmission; and/or a PUCCH resource identified by a PUCCH resourceindex. In an example, when a SR of a SR configuration triggered(therefore in pending now) in response to a BSR being triggered on a LCHcorresponding to the SR configuration, a wireless device may set aSR_COUNTER to a first value (e.g., 0), if there is no other pending SRscorresponding to the SR configuration.

In an example, a wireless device may determine whether there is at leastone valid PUCCH resource for the pending SR at the time of SRtransmission occasion. If there is no valid PUCCH resource for thepending SR, the wireless device may initiate a random access procedureon a PCell. The wireless device may cancel the pending SR in response tono valid PUCCH resource for the pending SR.

In an example, if there is at least one valid PUCCH resource for thepending SR, a wireless device may determine an SR transmission occasionon the at least one valid PUCCH resource based on the periodicity andthe offset of SR transmission. In an example, if the SR prohibit timeris running, the wireless device may wait for another SR transmissionoccasion. In an example, if the SR prohibit timer is not running; and ifthe at least one valid PUCCH resource for the SR transmission occasiondoes not overlap with a measurement gap; and if the at least one validPUCCH resource for the SR transmission occasion does not overlap with anuplink shared channel (UL-SCH) resource; if the SR_COUNTER is less thanthe maximum number of SR transmission, the wireless device may incrementthe SR_COUNTER (e.g., by one), instruct the physical layer of thewireless device to signal the SR on the at least one valid PUCCHresource for the SR. The physical layer of the wireless device maytransmit a PUCCH on the at least one valid PUCCH resource for the SR.The wireless device may monitor a PDCCH for detecting a DCI for uplinkgrant in response to transmitting the PUCCH.

In an example, if a wireless device receives one or more uplink grantswhich may accommodate all pending data available for transmission, thewireless device may cancel the pending SR, and/or stop the SR prohibittimer.

In an example, if the wireless device does not receive one or moreuplink grants which may accommodate all pending data available fortransmission, the wireless device may repeat one or more actionscomprising: determining the at least one valid PUCCH resource; checkingwhether the SR prohibit timer is running; whether the SR_COUNTER isequal or greater than the maximum number of SR transmission;incrementing the SR_COUNTER, transmitting the SR and starting the SRprohibit timer; monitoring a PDCCH for uplink grant.

In an example, if the SR_COUNTER indicates a number equal to or greaterthan the maximum number of SR transmission, a wireless device mayrelease PUCCH for one or more serving cells, and/or release SRS for theone or more serving cells, and/or clear one or more configured downlinkassignments and uplink grants, and/or initiate a random access procedureon a PCell, and/or cancel all the pending SRs.

In an example, a wireless device may be configured with one or more BWPsfor a serving cell (e.g., PCell, SCell). In an example, the serving cellmay be configured with at most a first number (e.g., four) BWPs. In anexample, for an activated serving cell, there may be one active BWP atany point in time.

In an example, a BWP switching for a serving cell may be used toactivate an inactive BWP and deactivate an active BWP at a time. In anexample, the BWP switching may be controlled by a PDCCH indicating adownlink assignment or an uplink grant. In an example, the BWP switchingmay be controlled by an inactivity timer (e.g. bwp-InactivityTimer). Inan example, the BWP switching may be controlled by a MAC entity inresponse to initiating a Random Access procedure. In an example, the BWPswitching may be controlled by an RRC signalling.

In an example, in response to RRC (re-)configuration offirstActiveDownlinkBWP-Id (e.g., included in RRC signaling) and/orfirstActiveUplinkBWP-Id (e.g., included in RRC signaling) for a servingcell (e.g., SpCell), the wireless device may activate a DL BWP indicatedby the firstActiveDownlinkBWP-Id and/or an UL BWP indicated by thefirstActiveUplinkBWP-Id, respectively without receiving a PDCCHindicating a downlink assignment or an uplink grant. In an example, inresponse to an activation of an SCell, the wireless device may activatea DL BWP indicated by the firstActiveDownlinkBWP-Id and/or an UL BWPindicated by the firstActiveUplinkBWP-Id, respectively without receivinga PDCCH indicating a downlink assignment or an uplink grant.

In an example, an active BWP for a serving cell may be indicated by RRCsignaling and/or PDCCH. In an example, for unpaired spectrum (e.g.,time-division-duplex (TDD)), a DL BWP may be paired with a UL BWP, andBWP switching may be common (e.g., simultaneous) for the UL BWP and theDL BWP.

In an example, for an active BWP of an activated serving cell (e.g.,PCell, SCell) configured with one or more BWPs, a wireless device mayperform, on the active BWP, at least one of: transmitting on UL-SCH onthe active BWP; transmitting on RACH on the active BWP if PRACHoccasions are configured; monitoring a PDCCH on the active BWP;transmitting, if configured, PUCCH on the active BWP; reporting CSI forthe active BWP; transmitting, if configured, SRS on the active BWP;receiving DL-SCH on the active BWP; (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 on the active BWPaccording to a stored configuration, if any, and to start in a symbolbased on some procedures.

In an example, for a deactivated BWP of an activated serving cellconfigured with one or more BWPs, a wireless device may not perform atleast one of: transmitting on UL-SCH on the deactivated BWP;transmitting on RACH on the deactivated BWP; monitoring a PDCCH on thedeactivated BWP; transmitting PUCCH on the deactivated BWP; reportingCSI for the deactivated BWP; transmitting SRS on the deactivated BWP,receiving DL-SCH on the deactivated BWP. In an example, for adeactivated BWP of an activated serving cell configured with one or moreBWPs, a wireless device may clear any configured downlink assignment andconfigured uplink grant of configured grant Type 2 on the deactivatedBWP; may suspend any configured uplink grant of configured Type 1 on thedeactivated (or inactive) BWP.

In an example, a base station may configure an activated serving cell ofa wireless device with a BWP inactivity timer.

In an example, the base station may configure the wireless device with adefault DL BWP ID for the activated serving cell (e.g., via RRCsignaling including defaultDownlinkBWP-Id parameter). In an example, anactive DL BWP of the activated serving cell may not be a BWP indicatedby the default DL BWP ID.

In an example, the base station may not configure the wireless devicewith a default DL BWP ID for the activated serving cell (e.g., via RRCsignaling including defaultDownlinkBWP-Id parameter). In an example, anactive DL BWP of the activated serving cell may not be an initialdownlink BWP (e.g., via RRC signaling including initialDownlinkBWPparameter) of the activated serving cell.

In an example, the BWP inactivity timer associated with the active DLBWP of the activated serving cell may expire.

In an example, the base station may configure the wireless device withthe default DL BWP ID. In an example, when the base station configuresthe wireless device with the default DL BWP ID, in response to the BWPinactivity timer expiring, a MAC entity of the wireless device mayperform BWP switching to a BWP indicated by the default DL BWP ID.

In an example, the base station may not configure the wireless devicewith the default DL BWP ID. In an example, when the base station doesnot configure the wireless device with the default DL BWP ID, inresponse to the BWP inactivity timer expiring, a MAC entity of thewireless device may perform BWP switching to the initial downlink BWP(e.g., initialDownlinkBWP in RRC signalling).

In an example, a wireless device may receive a PDCCH for a BWP switching(e.g., UL and/or DL BWP switching). In an example, a MAC entity of thewireless device may switch from a first active DL BWP of the activatedserving cell to a BWP (e.g., DL BWP) of the activated serving cell inresponse to the receiving the PDCCH. In an example, the switching fromthe first active DL BWP to the BWP may comprise setting the BWP as acurrent active DL BWP of the activated serving cell. In an example, thewireless device may deactivate the first active DL BWP in response tothe switching.

In an example, the base station may configure the wireless device with adefault DL BWP ID. In an example, the BWP may not be indicated (oridentified) by the default DL BWP ID. In an example, when the basestation configures the wireless device with the default DL BWP ID andthe MAC entity of the wireless device switches from the first active DLBWP of the activated serving cell to the BWP, the wireless device maystart or restart the BWP inactivity timer associated with the BWP (e.g.,the current active DL BWP) in response to the BWP not being the defaultDL BWP (or the BWP not being indicated by the default DL BWP ID).

In an example, the base station may not configure the wireless devicewith a default DL BWP ID. In an example, the BWP may not be the initialdownlink BWP of the activated serving cell. In an example, when the basestation does not configure the wireless device with the default DL BWPID and the MAC entity of the wireless device switches from the firstactive DL BWP of the activated serving cell to the BWP, the wirelessdevice may start or restart the BWP inactivity timer associated with theBWP (e.g., the current active DL BWP) in response to the BWP not beingthe initial downlink BWP.

In an example, when configured for operation in bandwidth parts (BWPs)of a serving cell, a wireless device (e.g., a UE) may be configured, byhigher layers with a parameter BWP-Downlink, a first set of BWPs (e.g.,at most four BWPs) for receptions, by the UE, (e.g., DL BWP set) in adownlink (DL) bandwidth for the serving cell.

In an example, when configured for operation in bandwidth parts (BWPs)of a serving cell, a wireless device (e.g., a UE) may be configured, byhigher layers with a parameter BWP-Uplink, a second set of BWPs (e.g.,at most four BWPs) for transmissions, by the UE, (e.g., UL BWP set) in auplink (UL) bandwidth for the serving cell.

In an example, the base station may provide a wireless device with ahigher layer parameter initialDownlinkBWP. In an example, an initialactive DL BWP may be provided by the higher layer parameterinitialDownlinkBWP in response to the providing.

In an example, a wireless device may have a dedicated BWP configuration.

In an example, in response to the wireless device having the dedicatedBWP configuration, the wireless device may be provided by a higher layerparameter (e.g., firstActiveDownlinkBWP-Id). The higher layer parametermay indicate a first active DL BWP for receptions.

In an example, in response to the wireless device having the dedicatedBWP configuration, the wireless device may be provided by a higher layerparameter (e.g., firstActiveUplinkBWP-Id). The higher layer parametermay indicate a first active UL BWP for transmissions on a carrier (e.g.,SUL, NUL) of a serving cell (e.g., primary cell, secondary cell).

In an example, for an unpaired spectrum operation, a DL BWP, from afirst set of BWPs, with a DL BWP index provided by a higher layerparameter bwp-Id (e.g., bwp-Id) may be linked with an UL BWP, from asecond set of BWPs, with an UL BWP index provided by a higher layerparameter bwp-Id (e.g., bwp-Id) when the DL BWP index of the DL BWP issame as the UL BWP index of the UL BWP.

In an example, a bandwidth part indicator field may be configured in aDCI format (e.g., DCI format 1_1, DCI format 0_1). In an example, avalue of the bandwidth part indicator field may indicate an active DL/ULBWP, from a first set of BWPs, for one or more DL/ULreceptions/transmissions. In an example, the bandwidth part indicatorfield may indicate a DL/UL BWP different from the active DL/UL BWP. Inan example, in response to the bandwidth part indicator field indicatingthe DL/UL BWP different from the active DL/ULBWP, the wireless devicemay set the DL/UL BWP as a current active DL/UL BWP. In an example, thesetting the DL/UL BWP as a current active DL/UL BWP may compriseactivating the DL/UL BWP and deactivating the active DL/UL BWP.

In an example, an active DL/UL BWP change may comprise switching fromthe active DL/UL BWP of a serving cell to a DL/UL BWP of the servingcell. In an example, the switching from the active DL/UL BWP to theDL/UL BWP may comprise setting the DL/UL BWP as a current active DL/ULBWP and deactivating the active DL/UL BWP.

In an example, for a serving cell (e.g., PCell, SCell), a base stationmay provide a wireless device with a higher layer parameterdefaultDownlinkBWP-Id. In an example, the higher layer parameterdefaultDownlinkBWP-Id may indicate a default DL BWP among the first setof (configured) BWPs of the serving cell.

In an example, a base station may not provide a wireless device with ahigher layer parameter defaultDownlinkBWP-Id. In response to not beingprovided by the higher layer parameter defaultDownlinkBWP-Id, thewireless device may set the initial active DL BWP as a default DL BWP.In an example, in response to not being provided by the higher layerparameter defaultDownlinkBWP-Id, the default DL BWP may be the initialactive DL BWP.

In an example, a base station may provide a wireless device with ahigher layer parameter BWP-InactivityTimer. In an example, the higherlayer parameter BWP-InactivityTimer may indicate a BWP inactivity timerwith a timer value for a serving cell (e.g., primary cell, secondarycell).

In an example, a base station may provide a wireless device with ahigher layer parameter firstActiveDownlinkBWP-Id of a serving cell(e.g., secondary cell). In an example, the higher layer parameterfirstActiveDownlinkBWP-Id may indicate a DL BWP on the serving cell(e.g., secondary cell). In an example, in response to the being providedby the higher layer parameter firstActiveDownlinkBWP-Id, the wirelessdevice may use the DL BWP as a first active DL BWP on the serving cell.

In an example, a base station may provide a wireless device with ahigher layer parameter firstActiveUplinkBWP-Id on a carrier (e.g., SUL,NUL) of a serving cell (e.g., secondary cell). In an example, the higherlayer parameter firstActiveUplinkBWP-Id may indicate an UL BWP. In anexample, in response to the being provided by the higher layer parameterfirstActiveUplinkBWP-Id, the wireless device may use the UL BWP as afirst active UL BWP on the carrier of the serving cell.

In an example, a UE may not monitor PDCCH when the UE performs RRMmeasurements over a bandwidth that is not within the active DL BWP forthe UE.

If a higher layer parameter firstActiveDownlinkBWP-Id is configured foran SpCell, a higher layer parameter firstActiveDownlinkBWP-Id indicatesan ID of a DL BWP to be activated upon performing the reconfiguration.

If a higher layer parameter firstActiveDownlinkBWP-Id is configured foran SCell, a higher layer parameter firstActiveDownlinkBWP-Id indicatesan ID of a DL BWP to be used upon MAC-activation of the SCell.

If a higher layer parameter firstActiveUplinkBWP-Id is configured for anSpCell, a higher layer parameter firstActiveUplinkBWP-Id indicates an IDof an UL BWP to be activated upon performing the reconfiguration.

If a higher layer parameter firstActiveUplinkBWP-Id is configured for anSCell, a higher layer parameter firstActiveUplinkBWP-Id indicates an IDof an UL BWP to be used upon MAC-activation of the SCell.

FIG. 17A shows example of a first beam failure scenario. In the example,a gNB may transmit a PDCCH from a transmission (Tx) beam to a receiving(Rx) beam of a wireless device from a TRP. When the PDCCH on the beampair link (between the Tx beam of the gNB and the Rx beam of thewireless device) have a lower-than-threshold RSRP/SINR value due to thebeam pair link being blocked (e.g., by a moving car or a building), thegNB and the wireless device may start a beam failure recovery procedureon the TRP.

FIG. 17B shows example of a second beam failure scenario. In theexample, the gNB may transmit a PDCCH from a beam to a wireless devicefrom a first TRP. When the PDCCH on the beam is blocked, the gNB and thewireless device may start a beam failure recovery procedure on a newbeam on a second TRP.

In an example, a wireless device may measure quality of beam pair linkusing one or more RSs. The one or more RSs may be one or more SSBs, orone or more CSI-RS resources. A CSI-RS resource may be identified by aCSI-RS resource index (CRI). In an example, quality of beam pair linkmay be defined as a RSRP value, or a reference signal received quality(e.g. RSRQ) value, and/or a CSI (e.g., SINR) value measured on RSresources. In an example, a gNB may indicate whether an RS resource,used for measuring beam pair link quality, is QCLed (Quasi-Co-Located)with DM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH maybe called QCLed when the channel characteristics from a transmission onan RS to a wireless device, and that from a transmission on a PDCCH tothe wireless device, are similar or same under a configured criterion.In an example, The RS resource and the DM-RSs of the PDCCH may be calledQCLed when doppler shift and/or doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are same.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of an uplink physical channel or signal fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (BFR-PUCCH); a PUSCH (e.g., BFR MAC-CE)and/or a contention-based PRACH resource (CF-PRACH). Combinations ofthese candidate signal/channels may be configured by the gNB. In anexample, when configured with multiple resources for a BFR signal, awireless device may autonomously select a first resource fortransmitting the BFR signal. In an example, when configured with aBFR-PRACH resource, a BFR-PUCCH resource, and a CF-PRACH resource, thewireless device may select the BFR-PRACH resource for transmitting theBFR signal. In an example, when configured with a BFR-PRACH resource, aBFR-PUCCH resource, and a CF-PRACH resource, the gNB may transmit amessage to the wireless device indicating a resource for transmittingthe BFR signal.

FIG. 18 shows an example flowchart of a BFR procedure. A wireless devicemay receive one or more RRC messages comprising BFR parameters. The oneor more RRC messages may comprise an RRC message (e.g. RRC connectionreconfiguration message, or RRC connection reestablishment message, orRRC connection setup message). The wireless device may detect at leastone beam failure according to at least one of BFR parameters. Thewireless device may start a first timer if configured in response todetecting the at least one beam failure. The wireless device may selecta selected beam in response to detecting the at least one beam failure.The selected beam may be a beam with good channel quality (e.g., RSRP,SINR, or BLER) from a set of candidate beams. The candidate beams may beidentified by a set of reference signals (e.g., SSBs, or CSI-RSs). Thewireless device may transmit at least a first BFR signal to a gNB inresponse to the selecting the selected beam. The at least first BFRsignal may be associated with the selected beam. The at least first BFRsignal may be a preamble transmitted on a PRACH resource, or a beamfailure recovery request (e.g., similar to scheduling request) signaltransmitted on a PUCCH resource, or a beam indication (e.g., BFR MAC CE)transmitted on a PUSCH resource. The wireless device may transmit the atleast first BFR signal with a transmission beam corresponding to areceiving beam associated with the selected beam. The wireless devicemay start a response window in response to transmitting the at leastfirst BFR signal. In an example, the response window may be a timer witha value configured by the gNB. When the response window is running, thewireless device may monitor a PDCCH in a first CORESET (e.g., UEspecific or dedicated to the wireless device or wireless devicespecific). The first CORESET may be associated with the BFR procedure.In an example, the wireless device may monitor the PDCCH in the firstCORESET in response to transmitting the at least first BFR signal. Thewireless device may receive a first DCI via the PDCCH in the firstCORESET when the response window is running. The wireless device mayconsider the BFR procedure successfully completed when receiving thefirst DCI via the PDCCH in the first CORESET before the response windowexpires. The wireless device may stop the first timer if configured inresponse to the BFR procedure successfully being completed. The wirelessdevice may stop the response window in response to the BFR proceduresuccessfully being completed.

In an example, when the response window expires, and the wireless devicedoes not receive the DCI, the wireless device may increment atransmission number, wherein, the transmission number is initialized toa first number (e.g., 0, 1) before the BFR procedure is initiated. Ifthe transmission number indicates a number less than the configuredmaximum transmission number, the wireless device may repeat one or moreactions comprising at least one of: a BFR signal transmission; startingthe response window; monitoring the PDCCH; incrementing the transmissionnumber if no response received during the response window is running. Ifthe transmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

In an example, a wireless device may trigger a beam failure recovery byinitiating a random-access procedure on a primary cell based ondetecting a beam failure. In an example, a wireless device may select asuitable/candidate beam for a beam failure recovery based on detecting abeam failure. In an example, the wireless device may determine that thebeam failure recovery is complete based on completion of therandom-access procedure.

FIG. 19 shows an example of a downlink beam failure recovery procedureas per an aspect of an embodiment of the present disclosure.

In an example, a base station may configure a medium-access control(MAC) entity of a wireless device with a beam failure recovery procedureby an RRC. The wireless device may detect a beam failure based on one ormore first RSs (e.g., SSB, CSI-RS). The beam failure recovery proceduremay be used for indicating to the base station of a candidate RS (e.g.,SSB or CSI-RS) when the wireless device detects the beam failure. In anexample, the wireless device may detect the beam failure based oncounting a beam failure instance indication from a lower layer of thewireless device (e.g. PHY layer) to the MAC entity.

In an example, a base station may reconfigure an information element(IE) beamFailureRecoveryConfig during an ongoing random-access procedurefor a beam failure recovery. In response to the reconfiguring the IEbeamFailureRecoveryConfig, the MAC entity may stop the ongoingrandom-access procedure. Based on the stopping the ongoing random-accessprocedure, the wireless device may initiate a second random-accessprocedure for the beam failure recovery using/with the reconfigured IEbeamFailureRecoveryConfig.

In an example, an RRC may configure a wireless device with one or moreparameters in an IE BeamFailureRecoveryConfig and an IERadioLinkMonitoringConfig for a beam failure detection and recoveryprocedure. The one or more parameters may comprise at least:beamFailureInstanceMaxCount for a beam failure detection;

beamFailureDetectionTimer for the beam failure detection;beamFailureRecoveryTimer for a beam failure recovery; rsrp-ThresholdSSB:an RSRP threshold for the beam failure recovery; PowerRampingStep forthe beam failure recovery; powerRampingStepHighPriority for the beamfailure recovery; preambleReceivedTargetPower for the beam failurerecovery; preambleTransMax for the beam failure recovery;scalingFactorBI for the beam failure recovery; ssb-perRACH-Occasion forthe beam failure recovery; ra-OccasionList for the beam failurerecovery; ra-ssb-OccasionMaskIndex for the beam failure recovery;prach-ConfigurationIndex for the beam failure recovery; andra-ResponseWindow. The ra-ResponseWindow may be a time window to monitorat least one response (e.g., random-access response, BFR response) forthe beam failure recovery. In an example, the wireless device may use acontention-free random-access preamble for the beam failure recovery.

FIG. 18 shows an example of a beam failure instance (BFI) indication. Inan example, a wireless device may use at least one UE variable for abeam failure detection. In an example, BFI_COUNTER may be one of the atleast one UE variable. The BFI_COUNTER may be a counter for a beamfailure instance indication. The wireless device may set the BFI_COUNTERinitially to zero.

In an example, a MAC entity of a wireless device may receive a beamfailure instance (BFI) indication from a lower layer (e.g. PHY) of thewireless device. Based on the receiving the BFI indication, the MACentity of the wireless device may start or restart thebeamFailureDetectionTimer (e.g., BFR timer in FIG. 18). Based on thereceiving the BFI indication, the MAC entity of the wireless device mayincrement BFI_COUNTER by one (e.g., at time T, 2T, 5T in FIG. 18).

In an example, the BFI_COUNTER may be equal to or greater than thebeamFailureInstanceMaxCount. Based on the BFI_COUNTER being equal to orgreater than the beamFailureInstanceMaxCount, the MAC entity of thewireless device may initiate a random-access procedure (e.g. on anSpCell) for a beam failure recovery.

In an example, in FIG. 18, the wireless device may initiate therandom-access procedure at time 6T, when the BFI_COUNTER is equal to orgreater than the beamFailureInstanceMaxCount (e.g., 3).

In an example, the wireless device may select an uplink carrier (e.g.,SUL, NUL) to perform the random-access procedure for the beam failurerecovery. In an example, the base station may configure an active uplinkBWP of the selected uplink carrier with IE beamFailureRecoveryConfig.When the wireless device initiates the random-access procedure for thebeam failure recovery, based on the active uplink BWP of the selecteduplink carrier being configured with the IE beamFailureRecoveryConfig,the wireless device may start, if configured, thebeamFailureRecoveryTimer. When the wireless device initiates therandom-access procedure for the beam failure recovery, based on theactive uplink BWP of the selected uplink carrier being configured withthe IE beamFailureRecoveryConfig, the wireless device may apply one ormore parameters (e.g., powerRampingStep, preambleReceivedTargetPower,and preambleTransMax) configured in the IE BeamFailureRecoveryConfig forthe random-access procedure.

In an example, the base station may configurepowerRampingStepHighPriority in the IE beamFailureRecoveryConfig. Whenthe wireless device initiates the random-access procedure for the beamfailure recovery and the active uplink BWP of the selected uplinkcarrier is configured with the IE beamFailureRecoveryConfig, based onthe powerRampingStepHighPriority being configured in the IEbeamFailureRecoveryConfig, the wireless device may setPREAMBLE_POWER_RAMPING_STEP to the powerRampingStepHighPriority.

In an example, the base station may not configurepowerRampingStepHighPriority in the IE beamFailureRecoveryConfig. Whenthe wireless device initiates the random-access procedure for the beamfailure recovery and the active uplink BWP of the selected uplinkcarrier is configured with the IE beamFailureRecoveryConfig, based onthe powerRampingStepHighPriority not being configured in the IEbeamFailureRecoveryConfig, the wireless device may setPREAMBLE_POWER_RAMPING_STEP to the powerRampingStep.

In an example, the base station may configure scalingFactorBI in the IEbeamFailureRecoveryConfig. When the wireless device initiates therandom-access procedure for the beam failure recovery and the activeuplink BWP of the selected uplink carrier is configured with the IEbeamFailureRecoveryConfig, based on the scalingFactorBI being configuredin the IE beamFailureRecoveryConfig, the wireless device may setSCALING_FACTOR_BI to the scalingFactorBI.

In an example, the base station may configure the active uplink BWP ofthe selected uplink carrier with the IE beamFailureRecoveryConfig. Basedon the active uplink BWP of the selected uplink carrier being configuredwith the IE beamFailureRecoveryConfig, the random-access procedure maybe a contention-free random-access procedure.

In an example, the base station may not configure the active uplink BWPof the selected uplink carrier with the IE beamFailureRecoveryConfig.Based on the active uplink BWP of the selected uplink carrier not beingconfigured with the IE beamFailureRecoveryConfig, the random-accessprocedure may be a contention-based random-access procedure.

In an example, the beamFailureDetectionTimer may expire. Based on thebeamFailureDetectionTimer expiring, the MAC entity of the wirelessdevice may set the BFI_COUNTER to zero (e.g., in FIG. 18, between time3T and 4T).

In an example, a base station may configure a wireless device with oneor more first RSs (e.g., SS/PBCH block, CSI-RS, etc.) for a beam failuredetection (e.g., by RadioLinkMonitoringRS in the IERadioLinkMonitoringConfig). In an example, the base station mayreconfigure the beamFailureDetectionTimer or thebeamFailureInstanceMaxCount or at least one RS of the one or more firstRSs by higher layers (e.g., RRC). Based on the reconfiguring, the MACentity of the wireless device may set the BFI_COUNTER to zero.

In an example, the wireless device may complete the random-accessprocedure (e.g., contention-free random-access or contention-basedrandom-access) for the beam failure recovery successfully. Based on thecompleting the random-access procedure successfully, the wireless devicemay determine/consider that the beam failure recovery is successfullycompleted.

In an example, the wireless device may complete the random-accessprocedure for the beam failure recovery successfully. Based on thecompleting the random-access procedure successfully, the wireless devicemay, if configured, stop the beamFailureRecoveryTimer. Based on thecompleting the random-access procedure successfully, the wireless devicemay set the BFI_COUNTER to zero.

In an example, the beamFailureRecoveryTimer may be running. In anexample, the base station may not configure the wireless device with thebeamFailureRecoveryTimer. In an example, the base station may providethe wireless device with one or more second RSs (e.g., SS/PBCH blocks,periodic CSI-RSs, etc.) for a beam failure recovery by a higher layerparameter candidateBeamRSList in the IE beamFailureRecoveryConfig. In anexample, the base station may provide the wireless device with one ormore uplink resources (e.g., contention-free random-access resources)for a beam failure recovery request (BFRQ) used in the beam failurerecovery by a higher layer (e.g., RRC) parameter (e.g.,candidateBeamRSList, ssb-perRACH-Occasion, ra-ssb-OccasionMaskIndex inthe IE beamFailureRecoveryConfig). An uplink resource of the one or moreuplink resources may be associated with a candidate RS (e.g., SSB,CSI-RS) of the one or more second RSs. In an example, the associationbetween the uplink resource and the candidate RS may be one-to-one.

In an example, at least one RS among the one or more second RSs may havea RSRP (e.g., SS-RSRP, CSI-RSRP) higher than a second threshold (e.g.,rsrp-ThresholdSSB, rsrp-ThresholdCSI-RS). In an example, the wirelessdevice may select a candidate RS among the at least one RS for the beamfailure recovery.

In an example, the candidate RS may be a CSI-RS. In an example, theremay be no ra-PreambleIndex associated with the candidate RS. Based onthe candidate RS being the CSI-RS and no ra-PreambleIndex beingassociated with the candidate RS, the MAC entity of the wireless devicemay set PREAMBLE_INDEX to an ra-PreambleIndex. The ra-PreambleIndex maybe associated/corresponding to an SSB in the one or more second RSs(e.g., indicated candidateBeamRSList). The SSB may be quasi-collocatedwith the candidate RS.

In an example, the candidate RS may be a CSI-RS and there may bera-PreambleIndex associated with the candidate RS. In an example, thecandidate RS may be an SSB. The MAC entity of the wireless device mayset PREAMBLE_INDEX to a ra-PreambleIndex, associated/corresponding tothe candidate RS, from a set of random-access preambles for the BFRQ. Inan example, a higher layer (RRC) parameter may configure the set ofrandom-access preambles for the BFRQ for the random-access procedure forthe beam failure recovery.

In an example, a MAC entity of a wireless device may transmit an uplinksignal (e.g., contention-free random-access preamble) for the BFRQ.Based on the transmitting the uplink signal, the MAC entity may start aresponse window (e.g., ra-ResponseWindow configured in the IEBeamFailureRecoveryConfig) at a first PDCCH occasion from the end of thetransmitting the uplink signal. Based on the transmitting the uplinksignal, the wireless device may, while the response window is running,monitor at least one PDCCH on a search space indicated byrecoverySearchSpaceId (e.g. of an SpCell) for a DCI. The DCI may beidentified by an RNTI (e.g., C-RNTI, MCS-C-RNTI) of the wireless device.

In an example, the MAC entity of the wireless device may receive, from alower layer (e.g., PHY) of the wireless device, a notification of areception of the DCI on the search space indicated by therecoverySearchSpaceId. In an example, the wireless device may receivethe DCI on a serving cell. In an example, the wireless device maytransmit the uplink signal via the serving cell. In an example, the DCImay be addressed to the RNTI (e.g., C-RNTI) of the wireless device. Inan example, based on the receiving the notification and the DCI beingaddressed to the RNTI, the wireless device may determine/consider therandom-access procedure being successfully completed.

In an example, the wireless device may transmit the uplink signal on anSpCell. In an example, the response window configured in the IEBeamFailureRecoveryConfig may expire. In an example, the wireless devicemay not receive a DCI (or a PDCCH transmission) addressed to the RNTI ofthe wireless device on the search space indicated byrecoverySearchSpaceId on the serving cell (e.g., before the responsewindow expires). Based on the response window expiring and not receivingthe DCI, the wireless device may consider a reception of a random-accessresponse (e.g., BFR response) unsuccessful. Based on the response windowexpiring and not receiving the DCI, the wireless device may increment atransmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) by one. In anexample, the transmission counter may be equal to preambleTransMax plusone. Based on the transmission counter being equal to thepreambleTransMax plus one and transmitting the uplink signal on theSpCell, the wireless device may indicate a random-access problem toupper layers (e.g., RRC).

In an example, the MAC entity of the wireless device may stop theresponse window (and hence monitoring for the random access response)after successful reception of the random-access response (e.g., the DCIaddressed to the RNTI of the wireless device, BFR response) in responseto the random access response comprising a random access preambleidentifier that matches the transmitted PREAMBLE_INDEX.

In an example, based on completion of a random-access procedure, a MACentity of a wireless device may discard explicitly signaledcontention-free random-access resources except one or more uplinkresources (e.g., contention-free random-access resources) for BFRQ.

In an example, a base station may provide a wireless device, for aserving cell (e.g., primary cell, secondary cell), with a first set ofresource configuration indexes (e.g., periodic CSI-RS resourceconfiguration indexes) by a higher layer parameterfailureDetectionResources (e.g., explicit beam failure detectionconfiguration). The first set of resource configuration indexes mayindicate one or more first RSs (e.g., CSI-RS, SS/PBCH block, etc.). Thebase station may configure the higher layer parameterfailureDetectionResources for a downlink BWP (of configured downlinkBWPs) of the serving cell. In an example, the base station may providethe wireless device, for the serving cell, with a second set of resourceconfiguration indexes (e.g., periodic CSI-RS resource configurationindexes, SS/PBCH block indexes) by a higher layer parametercandidateBeamRSList. The second set of resource configuration indexesmay indicate one or more second RSs (e.g., CSI-RS, SS/PBCH block, etc.).The base station may configure the higher layer parametercandidateBeamRSList for an uplink BWP (of configured uplink BWPs) of theserving cell. In an example, the wireless device may use the one or morefirst RSs and/or the one or more second RSs for radio link qualitymeasurements on the serving cell.

In an example, a base station may not provide a wireless device with ahigher layer parameter failureDetectionResources. Based on not beingprovided with the higher layer parameter failureDetectionResources, thewireless device may determine a first set of resource configurationindexes to include a resource configuration index (e.g., periodic CSI-RSresource configuration indexes) (e.g., implicit beam failure detectionconfiguration). In an example, the resource configuration index may besame as an RS index in a RS set. In an example, the RS index may beindicated by a TCI state (e.g., via a higher layer parameter TCI-state).In an example, the TCI state may be used for a control resource set(CORESET) that the wireless device is configured to monitor at least onePDCCH. In an example, the base station may configure the TCI state forthe CORESET. In an example, the TCI state may comprise two RS indexes.Based on the TCI state comprising two RS indexes, the first set ofresource configuration indexes may include an RS index, of the two RSindexes, with QCL-TypeD configuration. In an example, the base stationmay configure the TCI state for the CORESET.

In an example, the wireless device may expect the first set of resourceconfiguration indexes to include up to two RS indexes. The wirelessdevice may expect a single port RS in the first set of resourceconfiguration indexes. In an example, the one or more first RSs maycomprise up to two RSs indicated by the two RS indexes.

In an example, a first threshold (e.g. Qout, LR) may correspond to adefault value of higher layer parameter rlmInSyncOutOfSyncThreshold. Inan example, a second threshold (e.g. Qin, LR) may correspond to a valueprovided by higher layer parameter rsrp-ThresholdSSB in the IEBeamFailureRecoveryConfig.

In an example, a physical layer in a wireless device may assess a firstradio link quality of the one or more first RSs (or the first set ofresource configuration indexes) against the first threshold. In anexample, a first RS of the one or more first RSs may be associated (e.g.quasi co-located) with at least one DM-RS of a PDCCH monitored by thewireless device.

In an example, the wireless device may apply the second threshold to afirst L1-RSRP measurement obtained from a SS/PBCH block of the one ormore second RSs (or the second set of resource configuration indexes).In an example, the wireless device may apply the second threshold to asecond L1-RSRP measurement obtained from a CSI-RS of the one or moresecond RSs (or the second set of resource configuration indexes) afterscaling a reception power of the CSI-RS with a value provided by ahigher layer parameter powerControlOffsetSS.

In an example, a wireless device may assess the first radio link qualityof the one or more first RSs (indicated by the first set of resourceconfiguration indexes). A physical layer in the wireless device mayprovide a BFI indication to a higher layer (e.g. MAC) of the wirelessdevice when the first radio link quality is worse than the firstthreshold. In non-DRX mode operation, when the first radio link qualityis worse than the first threshold, the physical layer may inform thehigher layer with a first periodicity. The wireless device may determinethe first periodicity by the maximum between a shortest periodicityamong one or more periodicities of the one or more first RSs (e.g.,resource configurations in the first set) and a first value (e.g. 2msec). The first periodicity may be defined as max (the first value,TBFD-RS,M), where TBFD-RS,M is the shortest periodicity.

In an example, in DRX mode operation, when the first radio link qualityis worse than the first threshold, the physical layer may inform thehigher layer with a second periodicity. N an example, the base stationmay configure the wireless device with a DRX_cycle_length for the DRXmode operation. The wireless device may determine the second periodicityby max (1.5*DRX_cycle_length, 1.5*TBFD-RS,M) when the DRX_cycle_lengthis less than or equal to 320 ms. The wireless device may determine thatthe second periodicity is equal to the DRX_cycle_length when theDRX_cycle_length is greater than 320 ms.

In an example, based on a request from a higher layer (e.g. MAC) of thewireless device, the wireless device may provide to the higher layer oneor more candidate RSs (e.g., the periodic CSI-RS configuration indexes,the SS/PBCH blocks indexes) from the one or more second RSs (e.g., thesecond set) and one or more L1-RSRP measurements. In an example, eachcandidate RS of the one or more candidate RSs may be associated with aL1-RSRP measurement of the one or more L1-RSRP measurements. In anexample, the association may be one-to-one. In an example, the one ormore L1-RSRP measurements associated with the one or more candidate RSsmay be larger than or equal to the second threshold. In an example, thehigher layer may select a candidate RS (e.g., periodic CSI-RS resourceconfiguration, SS/PBCH block) among the one or more candidate RSs. In anexample, the candidate RS may be identified by a first RS index of thesecond set of resource configuration indexes. In an example, the firstRS index may indicate the candidate RS.

In an example, a wireless device may be provided/configured with acontrol resource set (CORESET) through a link to a search space set. TheCORESET may be UE specific or dedicated to the wireless device orwireless device specific. In an example, the wireless device may monitorthe CORESET for a beam failure recovery. In an example, the base stationmay provide the wireless device with the search space set by a higherlayer parameter recoverySearchSpaceId in the IEBeamFailureRecoveryConfig. The wireless device may monitor at least onePDCCH in the control resource set.

In an example, the base station may provide the wireless device with thehigher layer parameter recoverySearchSpaceId. Based on being providedwith the higher layer parameter recoverySearchSpaceId, the wirelessdevice may not expect to be provided with a second search space set formonitoring at least one PDCCH in the CORESET. In an example, the CORESETmay be associated with the search space set provided by the higher layerparameter recoverySearchSpaceId. Based on the CORESET being associatedwith the search space set provided by the higher layer parameterrecoverySearchSpaceId, the wireless device may not expect that theCORESET is associated with a second search space set.

In an example, the base station may provide the wireless device with aconfiguration for a transmission of an uplink signal (e.g., a PRACHtransmission) by a higher layer parameter PRACH-ResourceDedicatedBFR inthe IE BeamFailureRecoveryConfig. Based on the transmission of theuplink signal (e.g., the PRACH transmission) in a first slot (e.g., slotn) and, the wireless device, starting from a second slot (e.g., slotn+4), may monitor at least one PDCCH in a search space set (e.g.,provided by the higher layer parameter recoverySearchSpaceId) fordetection of a DCI format within a response window (e.g.,ra-responseWindow). In an example, the wireless device may monitor theat least one PDCCH in the search space set (or CORESET) according toantenna port quasi co-location parameters associated with the candidateRS (provided by the higher layer). In an example, the response windowmay be configured by the IE BeamFailureRecoveryConfig. The DCI formatmay be configured with CRC scrambled by a RNTI (e.g., C-RNTI,MCS-C-RNTI).

In an example, when the wireless device monitors at least one PDCCH inthe search space set (e.g., provided by the higher layer parameterrecoverySearchSpaceId) and for a reception of corresponding PDSCH, thewireless device may assume that antenna port quasi-collocationparameters for the at least one PDCCH and the corresponding PDSCH aresame as the candidate RS until the wireless device receives, by higherlayers, an activation for a TCI state or a higher layer parameterTCI-StatesPDCCH-ToAddlist and/or a higher layer parameterTCI-StatesPDCCH-ToReleaseList. In an example, a DCI format received inthe search space set while monitoring the at least one PDCCH mayschedule the corresponding PDSCH.

In an example, after the wireless device detects the DCI format with CRCscrambled by the RNTI (e.g., C-RNTI or MCS-C-RNTI) in the search spaceset (e.g., provided by the higher layer parameterrecoverySearchSpaceId), the wireless device may continue to monitor atleast one PDCCH in the search space set until the wireless devicereceives an activation command (e.g., MAC CE) for a TCI state or ahigher layer parameter TCI-StatesPDCCH-ToAddlist and/or a higher layerparameter TCI-StatesPDCCH-ToReleaseList.

In an example, the wireless device may perform the transmission of theuplink signal (e.g., PRACH transmission) on a serving cell (e.g., PCell,SCell). In an example, the wireless device may use a spatial filter forthe transmission of the uplink signal (e.g., preamble transmission forthe PRACH transmission). In an example, the wireless device may detect aDCI format, with CRC scrambled by the RNTI, in at least one PDCCH in thesearch space set (e.g., provided by the higher layer parameterrecoverySearchSpaceId). In an example, after a first number of symbols(e.g., 28 symbols) from a last symbol of a reception of the at least onePDCCH, the wireless device may transmit a second uplink signal via PUCCHon the serving cell using the spatial filter used for the transmissionof the uplink signal (e.g., the PRACH transmission) until the wirelessdevice receives an activation command (e.g., MAC CE) forPUCCH-Spatialrelationinfo or is provided PUCCH-Spatialrelationinfo forPUCCH resource(s) for the serving cell.

In an example, after a first number of symbols (e.g., 28 symbols) from alast symbol of a reception of the at least one PDCCH, the wirelessdevice may assume that antenna port quasi-collocation parameters for aCORESET with index zero (e.g., CORESET 0) are same as the candidate RSfor PDCCH monitoring in the CORESET with index zero.

In an example, the base station may not provide the wireless device iswith a higher layer parameter recoverySearchSpaceId. Based on not beingprovided with the higher layer parameter recoverySearchSpaceId, thewireless device may not initiate a contention-free random accessprocedure for a beam failure recovery. In an example, the wirelessdevice may initiate a contention-based random-access procedure for abeam failure recovery based on not being provided with the higher layerparameter recoverySearchSpaceId.

In an example, a wireless device may assess a downlink link quality of aserving cell based on one or more first RSs (e.g., periodic CSI-RS, SSB,etc.) in the first set of resource configuration indexes to detect abeam failure instance (BFI).

A wireless device may estimate a first radio link quality for an RS ofthe one or more first RSs and compare the first radio link quality to afirst threshold (Qout_LR) to access downlink radio link quality of theserving cell. The first threshold may be defined as a level at which adownlink radio level link may not be reliably received. In an example,the first threshold may correspond to a first percent (e.g., 10%) blockerror rate (BLER) of a hypothetical PDCCH transmission.

In an example, a wireless device may perform L1-RSRP measurements basedon one or more second RSs (e.g., periodic CSI-RS, SSB, etc.) in thesecond set of resource configuration indexes in order to detectcandidate beam (or candidate RS). An L1-RSRP measurement of thecandidate beam (or candidate RS) may be better than a second threshold(e.g., indicated by higher layer parameter rsrp-ThresholdSSB,rsrp-ThresholdCSI-rs (rsrp-ThresholdSSB+powerControlOffsetSS). UE is notrequired to perform candidate beam detection outside the active DL BWP.

A wireless device may perform a L1-RSRP measurement for an RS of the oneor more second RSs and compare the L1-RSRP measurement to the secondthreshold (rsrp-ThresholdSSB, rsrp-ThresholdCSI-rs) to select at leastone candidate beam (or candidate RS) for a beam failure recovery.

In an example, a wireless device may be active on a first DL BWP of aserving cell. The first DL BWP may be an active DL BWP of the servingcell based on being active on the first DL BWP. In an example, thewireless device may not perform a beam failure detection outside theactive DL BWP. In an example, the wireless device may not perform acandidate beam detection outside the active DL BWP. In an example, asecond DL BWP of the serving cell may be deactivated. The wirelessdevice may not perform a beam failure detection for the second DL BWPbased on the second DL BWP being deactivated. The wireless device maynot perform a candidate beam detection for the second DL BWP based onthe second DL BWP being deactivated.

In an example, a wireless device may estimate a first radio link qualityof a CSI-RS with a first subcarrier spacing (SCS) for a beam failuredetection. In an example, a wireless device may estimate a second radiolink quality of a SSB with a second subcarrier spacing (SCS) for a beamfailure detection. In an example, the wireless device may not performbeam failure detection measurements based on the first SCS and thesecond SCS being different. In an example, the wireless device may notperform beam failure detection measurements based on the CSI-RS and theSSB being frequency division multiplexes (FDM-ed) in at least one symbol(e.g., OFDM).

In existing beam failure recovery (BFR) procedures, a wireless devicemay perform a BFR procedure on an SpCell (e.g., PCell or PSCell). In anexample, a base station may transmit, to a wireless device, one or moremessages comprising configuration parameters of one or more cells. Theone or more cells may comprise at least one PCell/PSCell and one or moreSCells. In an example, an SpCell (e.g., PCell or PSCell) and one or moreSCells may operate on different frequencies and/or different bands.

In an example, an SCell of the one or more SCells may support amulti-beam operation. In the multi-beam operation, a wireless device mayperform one or more beam management procedures (e.g., a BFR procedure)on/for the SCell. The wireless device may perform a BFR procedure forthe SCell when at least one of one or more beam pair links between theSCell and the wireless device fails. Existing BFR procedures may resultin inefficiencies when there is a beam failure for the SCell. ExistingBFR procedures may be inefficient, take a long time, or increase batterypower consumption.

Example embodiments enhance existing BFR procedures to improve downlinkradio efficiency and reduce uplink signaling overhead when there is abeam failure for one or more SCells. For example, an example enhancedprocess uses a first cell random access resources when a beam failurefor an SCell of the one or more SCells occurs. In an example, downlinksignaling processes are enhanced for recovery of a beam failure for anSCell. In an example, uplink signaling is enhanced for a BFR procedureof the SCell.

Example embodiments provide processes for a wireless device and a basestation to enhance a BFR procedure for an SCell. Example embodiments mayreduce a duration of the BFR procedure and may reduce battery powerconsumption.

In an example, a wireless device may be configured with an SCell by abase station. The SCell may not have uplink resources. The SCell maycomprise downlink-only resources. When the wireless device detects abeam failure on the SCell. the wireless device may not transmit anuplink signal (e.g., preamble) for a BFR procedure of the SCell on theSCell in response to not having uplink resources. The wireless devicemay not perform a BFR procedure on the SCell. The base station may notbe aware of the beam failure on the SCell in response to the wirelessdevice not performing the BFR procedure. An example embodiment enhancesBFR procedures when an SCell comprises downlink-only resources.

In an example, an SCell may operate in a high frequency (e.g. 23 GHz, 60GHz, 70 GHz). In an example, an SpCell may operate in a low frequency(e.g. 2.4 GHz, 5 GHz). The channel condition of the SCell may bedifferent from the channel condition of the SpCell. The wireless devicemay use uplink resources of the SpCell to transmit a preamble for a beamfailure recovery request for the SCell, to improve robustness oftransmission of the preamble. An example embodiment enhances BFRprocedures when an SCell operates in a different frequency than PCell.An example embodiment enhances BFR procedures when an SCell used uplinkresources (e.g., random access resources, PUCCH resources, PUSCHresources, uplink BWPs of the PCell) of the PCell for a BFR procedure ofthe SCell.

FIG. 20 shows an example of a downlink beam failure recovery procedureof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

In an example, a wireless device may receive, from a base station, oneor more messages (at time T0 in FIG. 20). The one or more messages maycomprise one or more configuration parameters for a plurality of cells.The plurality of cells may comprise a first cell (e.g., PCell, PSCell,PUCCH SCell, SCell) and one or more secondary cells. The one or moresecondary cells may comprise a second cell (e.g., SCell, SCellconfigured with PUCCH).

In an example, the one or more messages may comprise one or more RRCmessages (e.g. RRC connection reconfiguration message, or RRC connectionreestablishment message, or RRC connection setup message).

In an example, the one or more configuration parameters may indicatecell-specific indices (e.g., provided by a higher layer parameterservCellIndex) for the plurality of cells. In an example, each cell ofthe plurality of cells may be identified by a respective onecell-specific index of the cell-specific indices. In an example, thefirst cell may be identified by a first cell-specific index of thecell-specific indices. In an example, the second cell may be identifiedby a second cell-specific index of the cell-specific indices.

In an example, the one or more configuration parameters may comprisebandwidth part (BWP) configuration parameters for a plurality of BWPs.The plurality of BWPs may comprise a first plurality of DL BWPs of thefirst cell and/or a first plurality of UL BWPs of the first cell. In anexample, the plurality of BWPs may comprise a second plurality of DLBWPs of the second cell and/or a second plurality of UL BWPs of thesecond cell. In an example, the first plurality of DL BWPs may comprisea first downlink BWP of the first cell. In an example, the firstplurality of UL BWPs may comprise a first uplink BWP of the first cell.In an example, the second plurality of DL BWPs may comprise a seconddownlink BWP of the second cell. In an example, the second plurality ofUL BWPs may comprise a second uplink BWP of the second cell.

In an example, the one or more configuration parameters may furthercomprise BWP specific indices for the plurality of BWPs. In an example,each BWP of the plurality of BWPs may be identified by a respective oneBWP specific index of the BWP specific indices (e.g., provided by ahigher layer parameter bwp-ID in the one or more configurationparameters).

In an example, the first downlink BWP may be identified by a first BWPspecific index of the BWP specific indices. The second downlink BWP maybe identified by a second BWP specific index of the BWP specificindices.

In an example, the one or more configuration parameters (e.g., RRC (BFR)in FIG. 19) may indicate one or more first RSs (e.g.,RadioLinkMonitoringRS provided in an IE RadioLinkMonitoringConfig) forthe second downlink BWP of the second cell (e.g., explicit BFDconfiguration).

In an example, for both explicit BFD configuration and the implicit BFDconfiguration, at least one RS of the one or more first RSs may betransmitted/configured on/in the first cell. In an example, for bothexplicit BFD configuration and the implicit BFD configuration, at leastone RS of the one or more first RSs may be transmitted/configured on/inthe second cell. In an example, for both explicit BFD configuration andthe implicit BFD configuration, at least one RS of the one or more firstRSs may be transmitted/configured on/in at least one of the one or moresecondary cells. In an example, transmitting/configuring the at leastone RS on the first cell and/or the at least one of the one or moresecondary cells may save overhead and save complexity of the wirelessdevice for tracking a high number of RSs.

In an example, at least one RS of the one or more first RSs may betransmitted/configured on/in the first cell. In an example, the secondcell and the first cell may share the at least one RS based on operatingin intra-band and/or QCL-ed (e.g., cross-carrier QCL) and/or based onsharing similar channel characteristics (e.g., Doppler spread, spatialfilter, etc.).

In an example, at least one RS of the one or more first RSs may betransmitted/configured on/in the second cell.

In an example, at least one RS of the one or more first RSs may betransmitted/configured on/in the at least one of the one or moresecondary cells. In an example, the second cell and the at least one ofthe one or more secondary cells may share the at least one RS based onoperating in intra-band and/or QCL-ed (e.g., cross-carrier QCL) and/orbased on sharing similar channel characteristics (e.g., Doppler spread,spatial filter, etc.).

In an example, the one or more first RSs may comprise one or more firstCSI-RSs. In an example, the one or more first RSs may comprise one ormore first SS/PBCH blocks. In an example, the one or more configurationparameters may indicate a maximum beam failure instance (BFI) counter(e.g., beamFailureInstanceMaxCount) (e.g., for the second cell, or forthe first cell or for the second downlink BWP of the second cell). In anexample, the wireless device may assess the one or more first RSs todetect a beam failure for the second downlink BWP of the second cell. Inan example, the one or more configuration parameters may indicate afirst threshold (e.g., provided by rlmInSyncOutOfSyncThreshold, Qout,LR) (e.g., for the second cell, or for the first cell or for the seconddownlink BWP of the second cell).

In an example, the one or more configuration parameters may indicate oneor more second RSs (e.g., candidateBeamRSList provided in IEBeamFailureRecoveryConfig) for the second downlink BWP of the secondcell. In an example, the wireless device may assess the one or moresecond RSs to select a candidate RS among the one or more second RSs fora beam failure recovery procedure of the second downlink BWP of thesecond cell.

In an example, the one or more second RSs may comprise one or moresecond CSI-RSs. In an example, the one or more second RSs may compriseone or more second SS/PBCH blocks.

In an example, the one or more configuration parameters may indicateRS-specific indices (e.g., provided by a higher layer parameterssb-index) for the one or more second RSs. In an example, each RS of theone or more second RSs may be identified by a respective one RS-specificindex of the RS-specific indices. In an example, a first RS of the oneor more second RSs may be identified by a first RS-specific index of theRS-specific indices. In an example, a second RS of the one or moresecond RSs may be identified by a second RS-specific index of theRS-specific indices.

In an example, at least one RS of the one or more second RSs may beconfigured/transmitted on/in the first cell. In an example, at least oneRS of the one or more second RSs may be configured/transmitted on/in thesecond cell. In an example, at least one RS of the one or more secondRSs may be configured/transmitted on/in at least one of the one or moresecondary cells. In an example, configuring the at least one RS of theone or more second RSs on the first cell and/or the at least one of theone or more secondary cells may save overhead and save complexity of thewireless device for tracking a high number of RSs.

In an example, at least one RS of the one or more second RSs may beconfigured/transmitted on/in the first cell. In an example, the secondcell and the first cell may share the at least one RS based on operatingin intra-band and/or QCL-ed (e.g., cross-carrier QCL) and/or based onsharing similar channel characteristics (e.g., Doppler spread, spatialfilter, etc.).

In an example, at least one RS of the one or more second RSs may beconfigured/transmitted on/in the second cell.

In an example, at least one RS of the one or more second RSs may beconfigured/transmitted on/in the at least one of the one or moresecondary cells. In an example, the second cell and the at least one ofthe one or more secondary cells may share the at least one RS based onoperating in intra-band and/or QCL-ed (e.g., cross-carrier QCL) and/orbased on sharing similar channel characteristics (e.g., Doppler spread,spatial filter, etc.).

In an example, the one or more configuration parameters may indicate asecond threshold (e.g., provided by rsrp-ThresholdSSB in the IEBeamFailureRecoveryConfig) for a beam failure recovery procedure of thesecond cell (or the second downlink BWP). In an example, the wirelessdevice may use the second threshold in a candidate beam selection of thesecond cell (or the second downlink BWP).

In an example, the one or more configuration parameters may indicate abeam failure recovery timer (e.g., provided by beamFailureRecoveryTimerin the IE BeamFailureRecoveryConfig) for a beam failure recoveryprocedure of the second cell (or the second downlink BWP).

In an example, the base station may configure the second threshold in aBWP (e.g., UL BWP, DL BWP) of the first cell. In an example, the basestation may configure the beam failure recovery timer in a BWP (e.g., ULBWP, DL BWP) of the first cell.

In an example, the base station may configure the second threshold in aBWP (e.g., UL BWP, DL BWP, the second downlink BWP) of the second cell.In an example, the base station may configure the beam failure recoverytimer in a BWP (e.g., UL BWP, DL BWP, the second downlink BWP) of thesecond cell.

In an example, the base station may configure the second threshold in aBWP (e.g., UL BWP, DL BWP) of at least one of the one or more secondarycells. In an example, the base station may configure the beam failurerecovery timer in a BWP (e.g., UL BWP, DL BWP) of at least one of theone or more secondary cells.

In an example, the base station may not provide the wireless device withreference signals for a candidate beam selection. In an example, the oneor more configuration parameters may not indicate one or more second RSs(e.g., candidateBeamRSList provided in IE BeamFailureRecoveryConfig) forthe second downlink BWP of the second cell. In an example, the wirelessdevice may not assess the one or more second RSs to select a candidateRS among the one or more second RSs for a beam failure recoveryprocedure of the second downlink BWP of the second cell. In an example,the wireless device may not perform a candidate beam selection for abeam failure recovery procedure of the second downlink BWP of the secondcell based on not being configured with the one or more second RSs.

In an example, the one or more configuration parameters may not indicatea second threshold (e.g., provided by rsrp-ThresholdSSB in the IEBeamFailureRecoveryConfig) for a beam failure recovery procedure of thesecond cell (or the second downlink BWP). In an example, the wirelessdevice may not perform a candidate beam selection for a beam failurerecovery procedure of the second downlink BWP of the second cell basedon not being configured with the second threshold.

In an example, the one or more configuration parameters may indicate asearch space set (e.g., provided by recoverySearchSpaceID in the IEBeamFailureRecoveryConfig). In an example, the search space set may belinked/associated with a control resource set (CORESET). In an example,the search space set may indicate the CORESET. In an example, thewireless device may monitor the CORESET for a beam failure recoveryprocedure of the second cell (or of the second downlink BWP). In anexample, the base station may configure the CORESET on the first cell.In an example, the base station may configure the CORESET on the secondcell. In an example, the base station may configure the CORESET on atleast one of the one or more secondary cells. In an example, thewireless device may monitor the search space set (e.g., linked to theCORESET) for a beam failure recovery procedure of the second downlinkBWP.

In an example, the second downlink BWP may be an active downlink BWP ofthe second cell. In an example, a physical layer in the wireless devicemay assess a first radio link quality of the one or more first RSs (fora beam failure detection of the second downlink BWP). The physical layermay provide a BFI indication to a higher layer (e.g. MAC) of thewireless device when the first radio link quality is worse (e.g., higherBLER, lower L1-RSRP, lower L1-SINR) than the first threshold.

In an example, the higher layer (e.g., MAC) of the wireless device mayincrement BFI_COUNTER by one in response to the physical layer providingthe BFI indication (e.g., at time T, 2T, 5T in FIG. 19). The BFI_COUNTERmay be a counter for a BFI indication. The wireless device may initiallyset the BFI_COUNTER to zero.

In an example, based on the incrementing the BFI_COUNTER, theBFI_COUNTER may be equal to or greater than the maximum BFI counter(e.g., beamFailureInstanceMaxCount). In an example, the wireless devicemay detect a beam failure of the second downlink BWP of the second cellbased on the BFI_COUNTER being equal to or greater than the maximum BFIcounter (time T1 in FIG. 20). In an example, the wireless device mayinitiate a beam failure recovery (BFR) procedure for the second downlinkBWP of the second cell based on the detecting the beam failure of thesecond downlink BWP (time T1 in FIG. 20). In an example, based on theinitiating the BFR procedure, the wireless device, if configured, maystart the beam failure recovery timer.

In an example, based on the initiating the BFR procedure, the wirelessdevice may initiate a candidate beam selection for the beam failurerecovery procedure (time T1 in FIG. 20). In an example, the wirelessdevice may initiate a candidate beam selection before initiating thebeam failure recovery procedure (e.g., before time T1 in FIG. 20,between time T0 and T1 in FIG. 20). In an example, the wireless devicemay initiate a candidate beam selection before detecting the beamfailure (e.g., before time T1 in FIG. 20, between time T0 and T1 in FIG.20). In an example, the wireless device may initiate a candidate beamselection based on being configured with the one or more second RSs(time T0 in FIG. 20). In an example, the wireless device may performbeam failure detection and candidate beam selection in parallel. In anexample, the wireless device may perform the candidate beam selectionduring the (ongoing) beam failure recovery procedure. In an example, thecandidate beam selection may comprise selecting/identifying a candidateRS (e.g., CSI-RS, SS/PBCH blocks) in/among the one or more second RSs(with quality higher than the second threshold).

In an example, the wireless device may initiate the candidate beamselection for the beam failure recovery procedure before the initiatingthe BFR procedure. In an example, the wireless device may initiate acandidate beam selection for the beam failure recovery procedure beforethe detecting the beam failure of the second downlink BWP. In anexample, the wireless device may perform one or more measurements on theone or more second RSs in parallel with estimating a first radio linkquality of the one or more first RSs.

In an example, the initiating the candidate beam selection may compriserequesting, by the higher layer from the physical layer, one or moreindices (of the RS-specific indices, for example, periodic CSI-RSconfiguration indexes and/or the SSB indexes provided by the one or moreconfiguration parameters) associated with one or more candidate RSsamong the one or more second RSs and/or one or more candidatemeasurements (e.g., L1-RSRP measurements) of the one or more candidateRSs. In an example, each measurement of the one or more candidatemeasurements may be better (e.g. lower BLER or higher L1-RSRP or higherL1-SINR) than the second threshold (e.g., rsrp-ThresholdSSB).

In an example, in the candidate beam selection, the physical layer ofthe wireless device may perform one or more measurements (e.g. L1-RSRPmeasurement) for the one or more second RSs. In an example, the wirelessdevice may perform each measurement of one or more measurements for acandidate RS of the one or more second RSs. In an example, the physicallayer may perform a first measurement of the one or more measurementsfor a first RS of the one or more second RSs. In an example, thephysical layer may perform a second measurement of the one or moremeasurements for a second RS of the one or more second RSs. In anexample, the physical layer may perform a third measurement of the oneor more measurements for a third RS of the one or more second RSs, andso on.

In an example, based on the performing the one or more measurements, thewireless device may determine that the one or more candidatemeasurements, of the one or more measurements, of the one or morecandidate RSs, of the one or more second RSs, are better (e.g. lowerBLER or higher L1-RSRP or higher SINR) than the second threshold (e.g.,rsrp-ThresholdSSB). In an example, each candidate RS of the one or morecandidate RSs has a candidate measurement (e.g., L1-RSRP), of the one ormore candidate measurements, better than the second threshold. In anexample, the first measurement for the first RS may be better (higherL1-RSRP) than the second threshold. In an example, the secondmeasurement for the second RS may be better (higher L1-RSRP) than thesecond threshold. In an example, the third measurement for the third RSmay be worse (lower L1-RSRP) than the second threshold. The one or morecandidate RSs may comprise the first RS and the second RS based on thefirst measurement and second measurement being better than the secondthreshold and the third measurement being worse than the secondthreshold. Based on the request, by the higher layer from the physicallayer, the physical layer may provide the first measurement and a firstRS-specific index of the first RS and the second measurement and asecond RS-specific index of the second RS.

In an example, based on the request, the physical layer of the wirelessdevice may provide, to the higher layer (e.g., MAC) of the wirelessdevice, one or more indices of the one or more candidate RSs (e.g., thefirst RS, the second RS) and one or more candidate measurements (e.g.,the first measurement, the second measurement) of the one or morecandidate RSs.

In an example, in response to receiving the one or more indices and theone or more candidate measurements associated with the one or morecandidate RSs, the higher layer (e.g., MAC) of the wireless device mayselect a candidate RS among the one or more candidate RSs. The higherlayer may indicate the candidate RS to the physical layer of thewireless device. In an example, the candidate RS may be identified witha candidate RS index (e.g., periodic CSI-RS configuration indexes and/orthe SSB indexes provided by the one or more configuration parameters) ofthe RS-specific indices (or of one or more indices of the RS-specificindices).

In an example, the one or more configuration parameters may indicateuplink physical channels (e.g., PUCCH, PRACH, PUSCH). In an example, theuplink physical channels may comprise physical random-access channels(PRACH) resources. In an example, the uplink physical channels maycomprise physical uplink control channel (PUCCH) resources. In anexample, the uplink physical channels may comprise physical uplinkshared channel (PUSCH) resources.

In an example, the wireless device may use (or transmit via at least oneuplink physical channel of) the uplink physical channels for a beamfailure recovery procedure of the second cell. In an example, the uplinkphysical channels may be dedicated to the beam failure recoveryprocedure of the second cell. In an example, when the wireless deviceinitiates a second beam failure recovery procedure for a third cell ofthe one or more secondary cells, the wireless may not transmit via theuplink physical channels for the second beam failure recovery procedureof the third cell based on the uplink physical channels being dedicatedto the second cell.

In an example, the uplink physical channels may be shared for beamfailure recovery procedure(s) of the one or more secondary cells. In anexample, when the wireless device initiates a second beam failurerecovery procedure for a third cell of the one or more secondary cells,the wireless may transmit via the uplink physical channels for thesecond beam failure recovery procedure of the third cell based on theuplink physical channels being shared for the one or more secondarycells.

In an example, the uplink physical channels may be dedicated for a beamfailure recovery procedure. In an example, the wireless device maytransmit an uplink signal based on initiating a beam failure recoveryprocedure. When the uplink physical channels are dedicated for the beamfailure recovery procedure, the wireless device may transmit the uplinksignal via the uplink physical channels based on the uplink signal beingfor the beam failure recovery procedure. In an example, the wirelessdevice may not transmit a second uplink signal (e.g., SR) via the uplinkphysical channels for a procedure other than a beam failure recoveryprocedure. In an example, the wireless device may not transmit a seconduplink signal (e.g., SR) via the uplink physical channels for requestinguplink resources to transmit a transport block (e.g., uplink data,UL-SCH, etc.).

In an example, the uplink physical channels may not be dedicated for abeam failure recovery procedure. In an example, the uplink physicalchannels may be shared for a beam failure recovery procedure and anotherprocedure (e.g., scheduling request, random-access, etc.). In anexample, the wireless device may transmit an uplink signal via theuplink physical channels for a beam failure recovery procedure. In anexample, the wireless device may transmit a second uplink signal (e.g.,SR) via the uplink physical channels for requesting uplink resources totransmit a transport block (e.g., uplink data, UL-SCH, etc.).

In an example, the uplink physical channels may be one-to-one associatedwith the one or more secondary cells. In an example, the wireless devicemay perform beam failure detection for a cell of the one or moresecondary cells when the cell is active. Each cell of the one or moresecondary cells may be associated with a respective uplink physicalchannel of the uplink physical channels. In an example, a first cell ofthe one or more secondary cells may be associated with a first uplinkphysical channel of the uplink physical channels. Based on theassociation, the wireless device may transmit a first uplink signal(e.g., SR, BFRQ, preamble, UCI, MAC CE, aperiodic CSI-RS, and the like)via the first uplink physical channel for a first BFR procedure of thefirst cell. Based on receiving the first uplink signal, the base stationmay be aware of the first BFR procedure of the first cell. In anexample, a second cell of the one or more secondary cells may beassociated with a second uplink physical channel of the uplink physicalchannels. Based on the association, the wireless device may transmit asecond uplink signal via the second uplink physical channel for a secondBFR procedure of the second cell. Based on receiving the second uplinksignal, the base station may be aware of the second BFR procedure of thesecond cell.

In an example, the base station may configure the uplink physicalchannels on the first cell. In an example, the base station mayconfigure the uplink physical channels on the second cell. In anexample, the base station may configure the uplink physical channels ona third cell (e.g., SCell with PUCCH) of the one or more secondarycells. In an example, the third cell may be different from the secondcell (e.g., a third cell-specific index of the third cell is differentfrom a second cell-specific index of the second cell).

In an example, the uplink physical channels may be dedicated to the beamfailure recovery procedure of the second cell. In response to beingdedicated to the beam failure recovery procedure of the second cell,when the base station receives an uplink signal (e.g., preamble viaPRACH, beam failure recovery request (BFRQ) transmission via PUCCH,scheduling request (SR) via PUCCH, BFR MAC-CE via PUSCH) via at leastone uplink physical channel (e.g., PUSCH, PRACH or PUCCH) of the uplinkphysical channels, the base station may be informed of the beam failurerecovery procedure of the second cell.

In an example, the uplink physical channels may not be dedicated to thebeam failure recovery procedure. When a base station receives an uplinksignal (e.g., the SR) via at least one uplink physical channel (e.g.,PUCCH) of the uplink physical channels, the base station may notdistinguish whether the uplink signal is transmitted for a beam failurerecovery procedure or for requesting uplink shared channel (UL-SCH)resources for an uplink transmission.

In an example, the wireless device may transmit an uplink signal (e.g.,preamble via PRACH, beam failure recovery request (BFRQ) transmissionvia PUCCH, scheduling request (SR) via PUCCH, MAC-CE via PUSCH,aperiodic CSI-RS via PUSCH) via at least one uplink physical channel(e.g., PRACH or PUCCH or PUSCH) of the uplink physical channels based oninitiating the beam failure recovery procedure for the second cell (attime T2 in FIG. 20).

In an example, the one or more configuration parameters may indicate aresponse window for the second cell (or for the second downlink BWP ofthe second cell). In an example, the one or more configurationparameters may indicate a maximum transmission counter (e.g.,sr-TransMax, bfrq-TransMax, preambleTransMax) for the second cell (orfor the second downlink BWP of the second cell).

In an example, the one or more configuration parameters may comprise oneor more CORESETs for the second downlink BWP of the second cell. In anexample, the wireless device may monitor the one or more CORESETs priorto the initiating the BFR procedure. In an example, the wireless devicemay not monitor the CORESET (e.g., dedicated for BFR procedure) prior tothe initiating the BFR procedure. In an example, the wireless device maymonitor the one or more CORESETs and the CORESET during the BFRprocedure. In an example, the wireless device may prioritize the CORESETover the one or more CORESETs during the BFR procedure. In an example,the prioritizing the CORESET over the one or more CORESETs may comprisethat the wireless device monitors the CORESET and depending on itscapability, the wireless device may monitor at least one CORESET of theone or more CORESETs.

In an example, the wireless device may start the response window (e.g.,ra-responseWindow, sr-prohibit timer, bfrq-prohibit timer), for adownlink control information (e.g., an uplink grant, triggeringaperiodic CSI-RS) from the base station, based on the transmitting theuplink signal. In an example, the wireless device may monitor, for theDCI from the base station, at least one PDCCH in the one or moreCORESETs within the response window (or while the response window isrunning).

In an example, the wireless device may increment a transmission counter(e.g., preamble_transmission_counter, sr-counter, bfrq-counter) by onebased on the transmitting the uplink signal. In an example, the wirelessdevice may set the transmission counter to an initial value (e.g., zero,one) based on the initiating the BFR procedure. In an example, thewireless device may retransmit the uplink signal until the transmissioncounter reaches to the maximum transmission counter.

In an example, the response window may expire. In an example, thewireless device may not receive the DCI within the response window(e.g., before the response window expires). Based on the response windowexpiring and the transmission counter being lower than the maximumtransmission counter, the wireless device may retransmit the uplinksignal, via at least one uplink physical channel of the uplink physicalchannels, for the BFR procedure.

In an example, the transmission counter may be equal to or higher thanthe maximum transmission counter. Based on the transmission counterbeing equal to or higher than the maximum transmission counter, thewireless device may initiate a random-access procedure (e.g.,contention-based random-access procedure).

In an example, based on the transmission counter being equal to orhigher than the maximum transmission counter, the wireless device maystop/reset the beam failure recovery timer. In an example, based on thetransmission counter being equal to or higher than the maximumtransmission counter, the wireless device may reset BFI_COUNTER to zero.

In an example, the wireless device may receive the DCI from the basestation at time T3 in FIG. 20. In an example, the wireless device mayreceive the DCI from the base station within the response window at timeT3 in FIG. 20.

In an example, the DCI may indicate uplink resources. In an example, theuplink resources may comprise time resources. In an example, the uplinkresources may comprise frequency resources.

In an example, the DCI may comprise an uplink grant. The uplink grantmay indicate the uplink resources.

In an example, the DCI may trigger a CSI report (e.g., aperiodic CSIreport). In an example, the DCI may comprise a CSI request fieldtriggering the CSI report. In an example, the uplink resources may beassociated with the CSI report.

In an example, the wireless device may transmit a second uplink signal(e.g., PUSCH, transport block, aperiodic CSI-report, UCI, PUCCH, MAC-CE,etc.) via uplink resources indicated by the DCI (at time T4 in FIG. 20).

In an example, the second uplink signal may be a MAC-CE (e.g., BFRMAC-CE, PHR MAC-CE, BSR, and the like). In an example, the second uplinksignal may be a layer-1 report. In an example, the second uplink signalmay be a CSI report (e.g., aperiodic CSI report).

In an example, the second uplink signal may comprise/indicate the secondcell-specific index of the second cell.

In an example, the wireless device may select/identify a candidate RS(of the one or more second RSs) associated/identified with a candidateRS index of the RS-specific indices for the BFR procedure. In anexample, the wireless device may select/identify the candidate RSthrough/in the candidate beam selection. In an example, based onselecting/identifying the candidate RS, the second uplink signal mayindicate the candidate RS index of the candidate RS.

In an example, the wireless device may initiate a BFR procedure for acell identified with a cell-specific index. The wireless device may, forthe BFR procedure of the cell, select/identify a candidate RS identifiedwith a candidate RS index. In an example, the second uplink signal maycomprise the cell-specific index. In an example, the second uplinksignal may comprise the candidate RS index.

In existing technologies, a base station may configure BFR proceduresfor a primary cell (e.g., PCell) and/or a secondary cell (e.g., SCell,or PScell) to a wireless device. In the BFR procedure of a primary cell(e.g., PCell), the base station may configure monitoring/failuredetection RSs (e.g., RadioLinkMonitoringRS provided in an IERadioLinkMonitoringConfig) transmitted on the primary cell. Based on theconfiguring the monitoring/failure detection RSs of the primary cell onthe primary cell, the monitoring/failure detection RSs (e.g.,RadioLinkMonitoringRS provided in an IE RadioLinkMonitoringConfig) areactive (e.g., BWP or cell for RS transmission is active) for the BFRprocedure for the primary cell (e.g., PCell). In the BFR procedure forthe secondary cell (e.g., SCell or PScell), the base station mayconfigure monitoring/failure detection RSs (e.g., RadioLinkMonitoringRSprovided in an IE RadioLinkMonitoringConfig) configured/transmitted on acell different from the secondary cell (e.g., PCell and/or anotherSCell). The base station may deactivate the cell. When the cell isdeactivated, there is no predefined procedure to support the BFRprocedure for the secondary cell (e.g., SCell or PScell). There is aneed to implement an enhanced procedure, e.g., when the cell whichtransmits monitoring/failure detection RSs (e.g., RadioLinkMonitoringRSprovided in an IE RadioLinkMonitoringConfig) is deactivated, to supportBFR procedures for the secondary cell (e.g., SCell or PScell).

Example embodiments implement an enhanced procedure when a firstsecondary cell (e.g., SCell or PScell), which transmitsmonitoring/failure detection RSs (e.g., RadioLinkMonitoringRS providedin an IE RadioLinkMonitoringConfig) for a BFR procedure of a secondsecondary cell, is deactivated. For example, a wireless device maydeactivate/stop/abort the BFR procedure when the first secondary cell isdeactivated. For example, when the first secondary cell is deactivated,the wireless device may determine monitoring/failure detection RSs(e.g., RadioLinkMonitoringRS provided in an IERadioLinkMonitoringConfig) based on TCI states of CORESETs of the secondsecondary cell. For example, the wireless device may determine one ofthe deactivation/stop/abort of the BFR procedure or the determination ofmonitoring/failure detection RSs (e.g., RadioLinkMonitoringRS providedin an IE RadioLinkMonitoringConfig) based on predefined conditions(e.g., frequency band of the first secondary cell and/or the secondsecondary cell). Example embodiments reduce power consumption orsignaling overhead for the BFR procedure of the second secondary cell atthe wireless device and/or base station.

FIG. 21 is an example diagram illustrating a BFR procedure in accordancewith embodiments of the present disclosure. FIG. 22 and FIG. 24 describeexample flow charts for a wireless device. FIG. 23 and FIG. 25 describeexample flow charts for a base station.

In an example, a base station may transmit an RRC message comprising aplurality of cells and BFR configuration parameters for the plurality ofcells. The plurality of cells may comprise a first cell and a secondcell. The BFR configuration parameters may indicate one or moremonitoring RSs (e.g., monitoring/failure detection RSs, and/or etc.) onthe first cell or on an active BWP of the first cell for a BFR procedureof the second cell. The first cell or the active BWP of the first cellmay be deactivated (e.g., based on the indication of the base stationand/or based on the BWP timer). Based on the deactivation of the firstcell or the active BWP of the first cell, the wireless device maydeactivate/stop/abort the BFR procedure of the second cell.

In an example, a base station may transmit an RRC message comprisingparameters for a plurality of cells, BFR configuration parameters forthe plurality of cells and TCI states of CORESETs for the plurality ofcells. The plurality of cells may comprise a first cell and a secondcell. The BFR configuration parameters may indicate one or moremonitoring RSs (e.g., monitoring/failure detection RSs, and/or etc.) onthe first cell or on an active BWP of the first cell for a BFR procedureof the second cell. The first cell or the active BWP of the first cellmay be deactivated (e.g., based on the indication of the base stationand/or based on the BWP timer). Based on the deactivation of the firstcell or the active BWP of the first cell, the wireless device maydetermine monitoring/failure detection RSs based on TCI states ofCORESETs of the second cell. Based on the determined monitoring/failuredetection RSs, the wireless device may start measuring the one or moremonitoring/failure detection RSs for a BFR procedure of the second cell.

In an example, a base station may transmit an RRC message comprisingparameters for a plurality of cells, BFR configuration parameters forthe plurality of cells and TCI states of CORESETs for the plurality ofcells. The plurality of cells may comprise a first cell, a second celland a third cell. The BFR configuration parameters may indicate one ormore monitoring RSs (e.g., monitoring/failure detection RSs, and/oretc.) on the first cell or on an active BWP of the first cell for a BFRprocedure of the second cell. The TCI states of CORESETs of the secondcell may comprise RSs on the third cell. The base station may deactivatethe first cell or the active BWP of the first cell.

Based on the deactivation of the first cell or the active BWP of thefirst cell, when predefined conditions are satisfied, the wirelessdevice may determine monitoring/failure detection RSs based on TCIstates of CORESETs of the second cell. Based on the deactivation of thefirst cell or the active BWP of the first cell, the wireless device maydetermine monitoring/failure detection RSs based on TCI states ofCORESETs of the second cell. Based on the determined monitoring/failuredetection RSs, the wireless device may start measuring the one or moremonitoring/failure detection RSs for a BFR of the second cell.

Based on the deactivation of the first cell or the active BWP of thefirst cell, when the predefined conditions are not satisfied, thewireless device may deactivate/stop/abort the BFR procedure of thesecond cell.

In an example, the predefined conditions may be a frequency range of athird cell. The base station may configure TCI states, of CORESETs ofthe second cell, which indicate RSs on the third cell. When thefrequency range of the third cell is different from the frequency rangeof the second cell (e.g., 3 GHz (i.e., Frequency Range 1) for the thirdcell and 28 GHz (i.e., Frequency Range 2) for the second cell), RSs onthe third cell may not be used for monitoring/detecting beam failure ofthe second cell due to different beams widths and channelcharacteristics. In this case, the wireless device maydeactivate/stop/abort the BFR procedure of the second cell. When thefrequency range of the third cell is adjacent from the frequency rangeof the second cell (e.g., 28 GHz (i.e., Frequency Range 2) for the thirdcell and 28 GHz (i.e., Frequency Range 2) for the second cell), the RSson the third cell may be used for monitoring/detecting beam failure ofthe second cell. In this case, the wireless device may measure/monitorthe RSs of TCI states of the CORESETs of the second cell for the BFRprocedure of the second cell.

In an example, the predefined conditions may be an intra band. The basestation may configure TCI states, of CORESETs of the second cell, whichindicate RSs on a third cell. When the base station configuresfrequencies of the third cell and the second cell on different frequencybands (inter band CA), RSs on the third cell may not be used formonitoring/detecting beam failure of the second cell due to differentbeams widths and channel characteristics. In this case, the wirelessdevice may deactivate/stop/abort the BFR procedure of the second cell.When the base station configures frequencies of the third cell and thesecond cell on same frequency band (e.g., intra band CA), the RSs on thethird cell may be used for monitoring/detecting beam failure of thesecond cell. In this case, the wireless device may measure/monitor theRSs of TCI states of the CORESETs of the second cell for the BFRprocedure of the second cell.

In an example, a base station may transmit an RRC message comprisingparameters for a plurality of cells and BFR configuration parameters forthe plurality of cells. The plurality of cells may comprise a first celland a second cell. The BFR configuration parameters may indicate one ormore monitoring RSs (e.g., monitoring/failure detection RSs, and/oretc.) on the first cell or on an active BWP of the first cell for a BFRprocedure of the second cell. The first cell or the active BWP of thefirst cell may be deactivated (e.g., based on the indication of the basestation and/or based on the BWP timer). Based on the deactivation of thefirst cell or the active BWP of the first cell, the wireless device mayindicate that the one or more monitoring/failure detection reference RSsare deactivated during the BFR procedure to the base station.

In an example, a base station may transmit an RRC message comprisingparameters for a plurality of cells and BFR configuration parameters.The plurality of cells may comprise a first cell, a second cell, a thirdcell and a fourth cell. The BFR configuration parameters may indicateone or more monitoring RSs (e.g., monitoring/failure detection RSs,and/or etc.) on the first cell and the fourth cell or on active BWPs ofthe first cell and the fourth cell for a BFR procedure of the secondcell. In an example, the enhanced procedure (i.e., thedeactivation/stop/abort of the BFR procedure of the second cell and/ormonitoring RSs of TCI states of CORESETs of the second cell) may bebased the deactivation of the first cell or the fourth cell (i.e., cellsfor monitoring RSs are partially deactivated). When the first cell orthe fourth cell is deactivated, the wireless device may support theenhanced procedure (i.e., the deactivation of the BFR procedure of thesecond cell, monitoring RSs of TCI states of CORESETs of the secondcell, the indication of the deactivated monitoring RSs). In an example,the enhanced procedure (i.e., the deactivation/stop/abort of the BFRprocedure of the second cell, monitoring RSs of TCI states of CORESETsof the second cell, the indication of the deactivated monitoring RSs)may be based on the deactivation of the first cell and the fourth cell(i.e., cells for monitoring RSs are all deactivated). When the firstcell and the fourth cell are deactivated, the wireless device maysupport the enhanced procedure (i.e., the deactivation/stop/abort of theBFR procedure of the second cell, monitoring RSs of TCI states ofCORESETs of the second cell, the indication of the deactivatedmonitoring RSs).

In an example, a wireless device may receive one or more messagescomprising configuration parameters of a plurality of cells comprising afirst cell and a second cell. The configuration parameters may indicateone or more monitoring reference signals (RSs) on the first cell for abeam failure recovery (BFR) procedure of the second cell. The wirelessdevice may deactivate the first cell. Based on the deactivating thefirst cell, the wireless device may deactivate the BFR procedure of thesecond cell. The wireless device may receive a deactivation message forthe deactivating the first cell. The wireless device may receive thedeactivation message via medium access control control element (MAC CE).The deactivating the first cell may be based on expiration of adeactivation timer of the first cell. The deactivating the first cellmay comprise a deactivation of a first bandwidth part (BWP) of the firstcell. The one or more monitoring RSs may be on the first BWP of thefirst cell. The deactivation of the first BWP may be based on expirationof a deactivation timer of the first BWP. The wireless device mayreceive a deactivation message for the deactivation the first BWP. Thewireless device may receive the deactivation message via MAC CE.

In an example, a wireless device may receive one or more messagescomprising configuration parameters of a plurality of cells comprising afirst cell and a second cell. The configuration parameters may indicateone or more monitoring reference signals (RSs) on the first cell for abeam failure recovery (BFR) procedure of the second cell. The wirelessdevice may deactivate the first cell. Based on the deactivating thefirst cell, the wireless device may measure RSs of control resource sets(CORESETs) of the second cell for the BFR procedure. The wireless devicemay receive a deactivation message for the deactivating the first cell.The wireless device may receive the deactivation message via mediumaccess control control element (MAC CE). The deactivating the first cellmay be based on expiration of a deactivation timer of the first cell.The deactivating the first cell may comprise a deactivation of a firstbandwidth part (BWP) of the first cell. The one or more monitoring RSsmay be on the first BWP of the first cell. The deactivation of the firstBWP may be based on expiration of a deactivation timer of the first BWP.The wireless device may receive a deactivation message for thedeactivation the first BWP. The wireless device may receive thedeactivation message via MAC CE. The one or more monitoring RSs maycomprise one or more channel state information-reference signals(CSI-RSs). The one or more CSI-RSs may comprise one or more periodicCSI-RSs. The one or more monitoring RSs may comprise one or moresynchronization signal blocks (SSBs). The measuring RSs of the CORESETsof the second cell may be based on transmission configuration indication(TCI) states of the CORSETs of the second cell.

In an example, a wireless device may receive one or more messagescomprising configuration parameters of a plurality of cells comprising afirst cell, a second cell and a third cell. The configuration parametersmay indicate one or more monitoring reference signals (RSs) on the firstcell for a beam failure recovery (BFR) procedure of the second cell. Thewireless device may deactivate the first cell. Based on the deactivatingthe first cell and a frequency of the third cell, the wireless devicemay deactivate the BFR procedure of the second cell or measure the BFRprocedure of the second cell via RSs of the third cell. The wirelessdevice may receive a deactivation message for the deactivating the firstcell. The wireless device may receive the deactivation message viamedium access control control element (MAC CE). The deactivating thefirst cell may be based on expiration of a deactivation timer of thefirst cell. The deactivating the first cell may comprise a deactivationof a first bandwidth part (BWP) of the first cell. The one or moremonitoring RSs may be on the first BWP of the first cell. Thedeactivation of the first BWP may be based on expiration of adeactivation timer of the first BWP. The wireless device may receive adeactivation message for the deactivation the first BWP. The wirelessdevice may receive the deactivation message via MAC CE. The RSs of thethird cell may comprise channel state information-reference signals(CSI-RSs) of the third cell. The CSI-RSs of the third cell may compriseperiodic CSI-RSs of the third cell. The RSs of the third cell maycomprise synchronization signal blocks (SSBs) of the third cell. Themeasuring the BFR procedure of the second cell via RSs of the third cellmay be based on transmission configuration indication (TCI) states ofthe CORSETs of the second cell. The frequency of third cell may comprisea frequency range of the third cell. The frequency of third cell maycomprise intra band carrier aggregation with the second cell. Thefrequency of third cell may comprise inter band carrier aggregation withthe second cell. The frequency of third cell may comprise subcarrierspacing of the third cell. The frequency of third cell may comprisecarrier frequency of the third cell.

In an example, a wireless device may receive one or more messagescomprising configuration parameters of a plurality of cells comprising afirst cell and a second cell. The configuration parameters indicate oneor more monitoring reference signals (RSs) on the first cell for a beamfailure recovery (BFR) procedure of the second cell. The wireless devicemay deactivate the first cell. Based on the deactivating the first cell,indicating the one or more monitoring RSs are deactivated during the BFRprocedure to a base station. The wireless device may receive adeactivation message for the deactivating the first cell. The wirelessdevice may receive the deactivation message via medium access controlcontrol element (MAC CE). The deactivating the first cell may be basedon expiration of a deactivation timer of the first cell. Thedeactivating the first cell may comprise a deactivation of a firstbandwidth part (BWP) of the first cell. The one or more monitoring RSsmay be on the first BWP of the first cell. The deactivation of the firstBWP may be based on expiration of a deactivation timer of the first BWP.The wireless device may receive a deactivation message for thedeactivation the first BWP. The wireless device may receive thedeactivation message via MAC CE. The one or more monitoring RSs maycomprise one or more channel state information-reference signals(CSI-RSs). The one or more CSI-RSs may comprise one or more periodicCSI-RSs. The one or more monitoring RSs may comprise one or moresynchronization signal blocks (SSBs). The wireless device may transmitphysical uplink control channel (PUCCH) for the indicating the one ormore monitoring RSs are deactivated. The wireless device may transmitphysical uplink control channel (PUSCH) for the indicating the one ormore monitoring RSs are deactivated. The wireless device may transmitmedium access control control element (MAC CE) for the indicating theone or more monitoring RSs are deactivated.

FIG. 29 is a flowchart of a BFR procedure as per an aspect of anembodiment of the present disclosure. At 2910, a wireless devicereceives configuration parameters indicating one or more first referencesignals (RSs), on a first cell, as candidate RSs for a beam failurerecovery (BFR) procedure of a second cell. At 2920, the wireless devicetriggers, in response to a number of beam failure instances on thesecond cell, the BFR procedure for the second cell. At 2930, thewireless device deactivates the first cell. At 2940, the wireless devicecancels, based on the deactivating the first cell, the BFR procedure forthe second cell.

According to an example embodiment, the wireless device measures (orassesses) the one or more first RSs, on the first cell, for a candidatebeam selection for the BFR procedure of the second cell, based on thefirst cell being in active state.

According to an example embodiment, the wireless device deactivates thefirst cell in response to at least one of: an expiry of a celldeactivation timer of the first cell and/or receiving a MAC CE (e.g.,SCell activation/deactivation MAC CE) indicating a deactivation of thefirst cell.

According to an example embodiment, the wireless device triggers the BFRprocedure comprises triggering a scheduling request for the BFRprocedure of the second cell.

According to an example embodiment, the wireless device, based oncancelling the BFR procedure for the second cell, stops measuring theone or more first RSs, on the first cell, for a candidate beam selectionfor the BFR procedure of the second cell.

According to an example embodiment, the wireless device receives one ormore radio resource control messages comprising the configurationparameters, the configuration parameters further indicating: one or moresecond RSs, on the second cell, for beam failure instance detection forthe BFR procedure of the second cell; one or more scheduling request forthe BFR procedure of the second cell; a radio link quality threshold anda maximum beam failure instance counter. The wireless device triggersthe BFR procedure, for the second cell, based on: determining a beamfailure instance being detected based on the one or more second RSsbeing assessed with radio quality lower than the radio link qualitythreshold and the number of beam failure instances reaching to themaximum beam failure instance counter.

According to an example embodiment, the wireless device triggers atransmission of a scheduling request based on the triggering the BFRprocedure of the second cell. The wireless device transmits thescheduling request for the BFR procedure of the second cell via aphysical uplink control channel. The wireless device, based on thecancelling the BFR procedure, stops the transmission of the schedulingrequest.

According to an example embodiment, a wireless device may receiveconfiguration parameters indicating one or more first reference signals(RSs) on the first cell for a beam failure recovery (BFR) procedure of asecond cell. The wireless device may measure, for the BFR procedure ofthe second cell, at least one of the one or more first RSs on the firstcell. The wireless device may deactivate the first cell. The wirelessdevice may measure, based on the deactivating the first cell and for theBFR procedure of the second cell, second RSs of control resource sets ofthe second cell.

According to an example embodiment, a wireless device may receiveconfiguration parameters of a plurality of cells comprising a firstcell, a second cell and a third cell, wherein the configurationparameters indicate one or more first reference signals (RSs) on thefirst cell for a beam failure recovery (BFR) procedure of the secondcell. The wireless device may measure the one or more RSs of the firstcell for the BFR procedure of the second cell. The wireless device maydeactivate the first cell. The wireless device may measure, based onconfiguration parameters of a third cell and the deactivating the firstcell, second RSs of the third cell for the BFR procedure of the secondcell.

According to an example embodiment, a wireless device may receive one ormore messages comprising configuration parameters of a plurality ofcells comprising a first cell and a second cell, wherein theconfiguration parameters indicate one or more monitoring referencesignals (RSs) on the first cell for a beam failure recovery (BFR)procedure of the second cell. The wireless device may deactivate thefirst cell. The wireless device may, based on the deactivating the firstcell, indicate the one or more monitoring RSs are deactivated during theBFR procedure to a base station.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters indicating one or more first referencesignals (RSs), on a first cell, as candidate RSs for a beam failurerecovery (BFR) procedure of a second cell; triggering, in response to anumber of beam failure instances on the second cell, the BFR procedurefor the second cell; deactivating the first cell; and cancelling, basedon the deactivating the first cell, the BFR procedure for the secondcell.
 2. The method of claim 1, further comprising measuring the one ormore first RSs, on the first cell, for a candidate beam selection forthe BFR procedure of the second cell, based on the first cell being inactive state.
 3. The method of claim 1, wherein the wireless devicedeactivates the first cell in response to at least one of: an expiry ofa cell deactivation timer of the first cell; and receiving a mediumaccess control control element indicating a deactivation of the firstcell.
 4. The method of claim 1, wherein the triggering the BFR procedurecomprises triggering a scheduling request for the BFR procedure of thesecond cell.
 5. The method of claim 1, wherein the cancelling the BFRprocedure for the second cell comprises stopping measuring the one ormore first RSs, on the first cell, for a candidate beam selection forthe BFR procedure of the second cell.
 6. The method of claim 1, furthercomprising receiving one or more messages comprising the configurationparameters, the configuration parameters further indicating: one or moresecond RSs, on the second cell, for beam failure instance detection forthe BFR procedure of the second cell; one or more scheduling requestsfor the BFR procedure of the second cell; a radio link qualitythreshold; and a maximum beam failure instance counter.
 7. The method ofclaim 6, further comprising triggering the BFR procedure, for the secondcell, based on: detecting a beam failure instance based on the one ormore second RSs being assessed with a radio quality lower than the radiolink quality threshold; and the number of beam failure instancesreaching the maximum beam failure instance counter.
 8. The method ofclaim 1, further comprising triggering a transmission of a schedulingrequest based on the triggering the BFR procedure of the second cell. 9.The method of claim 8, wherein the wireless device transmits thescheduling request for the BFR procedure of the second cell via aphysical uplink control channel.
 10. The method of claim 8, wherein thecancelling the BFR procedure comprises stopping the transmission of thescheduling request.
 11. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receiveconfiguration parameters indicating one or more first reference signals(RSs), on a first cell, as candidate RSs for a beam failure recovery(BFR) procedure of a second cell; trigger the BFR procedure for thesecond cell in response to a number of beam failure instances on thesecond cell; deactivate the first cell; and cancel, based on thedeactivation of the first cell, the BFR procedure for the second cell.12. The wireless device of claim 11, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to measure the one or more first RSs, on the first cell, for acandidate beam selection for the BFR procedure of the second cell, basedon the first cell being in active state.
 13. The wireless device ofclaim 11, wherein the instructions, when executed by the one or moreprocessors cause the wireless device to deactivate the first cell inresponse to at least one of: an expiry of a cell deactivation timer ofthe first cell; and reception of a medium access control control elementindicating a deactivation of the first cell.
 14. The wireless device ofclaim 11, wherein the triggering of the BFR procedure comprisestriggering a scheduling request for the BFR procedure of the secondcell.
 15. The wireless device of claim 11, wherein the cancellation ofthe BFR procedure for the second cell comprises stopping the measurementof the one or more first RSs, on the first cell, for a candidate beamselection for the BFR procedure of the second cell.
 16. The wirelessdevice of claim 11, wherein the instructions, when executed by the oneor more processors, further cause the wireless device to receive one ormore radio resource control messages comprising the configurationparameters of the second cell, the configuration parameters furtherindicating: one or more second RSs, on the second cell, for beam failureinstance detection for the BFR procedure of the second cell; one or morescheduling requests for the BFR procedure of the second cell; a radiolink quality threshold; and a maximum beam failure instance counter. 17.The wireless device of claim 16, wherein the wireless device triggeringthe BFR procedure, for the second cell, is based on: a detection of abeam failure instance based on the one or more second RSs being assessedwith a radio quality lower than the radio link quality threshold; andthe number of beam failure instances reaching the maximum beam failureinstance counter.
 18. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to trigger a transmission of a scheduling requestbased on the triggering the BFR procedure of the second cell.
 19. Thewireless device of claim 18, wherein the cancelling the BFR procedurecomprises stopping the transmission of the scheduling request.
 20. Asystem comprising: a base station comprising: one or more firstprocessors; and memory storing first instructions that, when executed bythe one or more first processors, cause the base station to: transmitconfiguration parameters indicating one or more first reference signals(RSs), on a first cell, as candidate RSs for a beam failure recovery(BFR) procedure of a second cell; and a wireless device comprising: oneor more second processors; and memory storing second instructions that,when executed by the one or more second processors, cause the wirelessdevice to: receive the configuration parameters; trigger the BFRprocedure for the second cell in response to a number of beam failureinstances on the second cell; deactivate the first cell; and cancel,based on the deactivation of the first cell, the BFR procedure for thesecond cell.